>> > I promise you, this is the last time I will respond to you, > the original link I sent you > http://tomcat.apache.org/tomcat-6.0-doc/config/manager.html > * > now scroll down until you see > org.apache.catalina.session.PersistentManager > > did you even get that far down the document, cause you don't sound like > you did
Regardless of whether or not you respond, I still have a question for development. I'll take full blame as it may not be clear what I want to do. What I want to do seems is not easily done with the current Manager/Store source. First, all the storage classes, from what I can see, leave the session object alive and local on the server. There is a strong assumption the the session will be local to one box. If you look at code it seems that the sessions are only written when they are "pasivated" or expire. There does not seem to be direct way for the storage system to be notified when the current servlet is done with its session, only when it expires. It seems a java session must expire before it is written to the storage system. This doesn't work in a cluster without the load balancer ensuring that session are sticky to a particular machine, UNLESS you use the clustering system which replicates the session to all machines. This isn't a question about "how to use" the system in my servlet, it is a question about the best approach to implement different functionality in the server. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
