Shahed Ali wrote:
 Hi, Thanks for the insight, but what I meant was will Tomcat automatically  serialise a session if it grows too large ?Or will it do so only if the server is ready to shutdown. I do NOT want my session data to be serailzed without my knowing . ThanksShahed. 


At present, Tomcat 3.2 and 4.0 *only* serialize sessions across a server restart (either because you shut Tomcat down manually, or because it was triggered by an auto-reload due to a changed class).  In both cases, you can turn this feature off with appropriate server.xml configuration settings.

In the servlet 2.3 API (implemented by Tomcat 4.0), there is a new application event listener interface (HttpSessionActivationListener) that is used to declare application classes that want to be notified when a session is about to be passivated (i.e. serialized out), or when it has been reloaded -- possibly in a different JVM.  If/when Tomcat 4.0 supports session serialization at other times, it will fire these events so that your application will know about them.

Craig McClanahan
 

Reply via email to