Re: Overwhelming a Web Application Server

[Pete Helgren <Pete@xxxxxxxxxx>]

I think the settings we are working with are in server.xml although I 
could be wrong.  Same concept though. Also if the user takes the option 
to log out (Ha!) then I issue a session.invalidate() to clean up.

Your post about a limit to sessions and a notification rather than a 
"stall" is a good idea.  We are running into an issue where commons 
pooling is deadlocking and sessions are growing while waiting in Tomcat 
and the login to the application just hangs because Tomcat has reached 
the max.  I'll have to look into method that would tell the app that 
Tomcat has exceeded the session threshold and issue a "Server not 
available - please try again later" page.

Pete


Nathan Andelin wrote:
> > From: Pete Helgren
> > I keep the session timeout value relatively low so that sessions expire 
> > and are GC'ed on a regular basis ...
> >     
>
>
> Thorbjoern just explained the <session timeout> tag in the web.xml file.  Is that the way you expire sessions?
>
> Nathan.
>
>
>
>       
>