asp.net - random IIS session timeout -
I have a very awkward problem and I'm looking for any advice, an ASP running away from IS6. Net website that works well for the most part. However, sessions are being randomly cleared? So if I login ... click around, I've been booted randomly. Sometimes it happens after 30 seconds / 4 clicks, sometimes this is the first click, sometimes it's me Will not even login ... and sometimes it works fine ?? (The reason I know this is getting cleared because I print the session when I log off, and they are empty)
I have taken a look at the IIS log, but they do not tell me much I suspect it may be a timezone problem ?, .. I was wondering if anyone has any information about whether it is a possibility or not?
Besides, any tips about getting more information about what is happening in the session?
The most awkward part about my problem so far is this randomness which will probably work as a good clue for the cause of an IIS / ASP.NET expert. (At least I hope so!)
Another clue: When I host it locally, then the site works properly, and I only get the problem when I I host a Virtual Godaddy server (which is running IIS 6)
One more thing I saw
My cookies appear on the local host like this. : (From firebug) cookie ASP.NT_SessionId = vgt4ly45frvsm1qsfjsmdcbc; User name =; Demo = true
On the hosted server this is just: cookie ASP.NT_SessionId = vgt4ly45frvsm1qsfjsmdcbc;
"Username" is the name of my session ... Maybe I have cookies disabled on shared hosting and this session is not working?
Thank you for your time, Andrew
Recycling your asp.net application can be done. Recycling can occur when a memory or CPU threshold arrives, or after some time (15 minutes inactivity to be used by default on IIS 6).
When the application gets recycled, everything in memory is lost so that you may lose the session data.
To ensure that recycling is a criminal, you can view the display counter on your server or just log something in the application_start global.asax handler.
For a list of asp.net display counters on IIS6, check
"Restart the application" and counter the "Worker process restart", they are the ones you should look on .
Comments
Post a Comment