Sorry for being a little vague. The application is a thin client containing a presentation layer which communicates events over SOAP to the server. Therefore only the presentation code is maintained on the client and all events and database retrieval is handled by the server.
The problem is if the client is idle for a certain amount of time, I would want the server to shut down it's connection and free itself. The next client connection would result in a redirect to a login screen.
The session nature of the program means that for every client connection, a new server object is created. This server object then establishes database connections as well as preforming a lot of processing. The ideal situation would be each server instance to die cleanly if the client has timed out. I realise that this may have to be coded by me but it would be nice if this behaviour existed already.
How would I get access to the HttpSession object without hacking the SOAP code?? I am not using an Apache SOAP client so adding extra parameters to the request is not an ideal solution.
Thanks.
 
-----Original Message-----
From: Erich Izdepski [mailto:[EMAIL PROTECTED]]
Sent: 20 May 2002 14:45
To: [EMAIL PROTECTED]
Subject: RE: Session Timeouts

Phillip-
What type of application is this? If servlet based, session timeout and cleanup activities are controlled by the HttpSession, HttpSessionBindingEvent, and HttpSessionBindingListener classes of the java.servlet.http package.
 
If there is more to these problem, these provide the details.

Erich

-----Original Message-----
From: Phillip Urrea [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 20, 2002 5:23 AM
To: '[EMAIL PROTECTED]'
Subject: Session Timeouts

Our application is running in session scope on the server. Does anyone know of anyway the server can timeout when the client is inactive for a period of time. I would like to have a way of closing the server neatly and redirecting the client if they've been inactive for too long.
Thanks,
Phillip.

Reply via email to