Re: Overwhelming a Web Application Server

[Nathan Andelin <nandelin@xxxxxxxxx>]

> From: Thorbjoern Ravn Andersen
> One way to approach this, is to kill idle sessions ...

Of course.  Session data and objects may be consuming a lot of memory.  And it might make sense to release it after a period of inactivity - depending on the application.  But what I was hoping that you might explain is whether that's a function of the application that the developer must code, or part of a framework, or some sort of configuration setting in an application server?  An optional setting for each application, or JSP, or Servlet, or Session Manager, or whatever?

> Another approach used AFAIK in Apache Tomcat and other
> Java web servers is to persist the oldest sessions to disk ...

And the same questions apply here.  Code that into the application?  Use a framework?  A configuration setting in Tomcat?  Does serializing an object automatically release memory?

Thanks,

Nathan.