Last post Nov 30, 2010 03:37 PM by Doctor Data
Nov 30, 2010 01:58 PM|Doctor Data|LINK
(I don't know which forum to post this. The applet-specific posts I found are all over the place. I'm hoping the readers of this forum are particularly knowledgeable
I've got a Java applet that runs in an ASP.NET web site. Whenever the user interacts with the applet, I make a request to the server for a small web page (.aspx file) that exists precisely to reset the session time clock. I have the proper session id in
the request cookies (I know it's correct because the applet uses services on the server and those services get the right session object) and the file I get is the result of the aspx page's having been processed -- well formatted html. However,
the session dies anyway. Retrieving the web page doesn't reset the session timer.
Now, the only request header in my request is the cookies. I'm wondering if I don't need more. Such as the Referrer? or the Connection keep-alive? (although I always thought that had to do with TCP/IP, not ASP.NET sessions).
Or is there something else I need to do to make the session take notice?
Nov 30, 2010 03:07 PM|sachingusain|LINK
Is your worker process/app domain recycling due to some other reason (like too much load, changes in web.config etc)? That might be one of the reason why session is getting killed (without being timed out).
Nov 30, 2010 03:37 PM|Doctor Data|LINK
Doesn't look that way. I tested by clicking every 5 minutes (which downloaded the file) and then 2 minutes after the time out period. And there've been other reports of session ending prematurely. The web site is a lightly used development server.