Hi List, I found something, that looked promising, but did not work. Developers, please look, this could be a bug:
The deploy-task has an attribute "update", removes the context before re-installing it. I hoped that this one would do what I want. But unfortunately, it is equivalent to undeploy/deploy so my sessions are gone again. :-( Maybe I have to clarify, what I am doing with my sessions (for Rodrigo): I have all session-attribute in my application serializable, so that tomcat can save all session data to disk when the context or tomcat itself is stopped. At startup these serialized data is being read back by tomcat automatically. As a result, users can coutinue their work exactly where the are. (Except that the application is not available for 1-2 seconds. But it is still unlikely that a users fires a request just in this moment, at least for medium-frequency apps) Formerly, the persisted session data survived the remove, so I could re-install the app. Please help! Reinhard Am Dienstag, 14. März 2006 13:53 schrieb Reinhard Moosauer: > Hello List, > > recently I upgraded from tomcat 5.5.9 to 5.5.15 > Since then, all my sessions are lost after a remove/install via the > manager. > > The problem is the following: > I installed a war-file, which is copied to the webapps-folder during > manager-install. When I want to replace the war with a new version, I > _have_ to undeploy, which deletes my persistent sessions too. > > How can I get back the smooth behavior of 5.5.9, which allowed me an > application update on the fly without disturbing user sessions? > > many thanks in advance for your advice > > Reinhard > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
