I found another thread which indicates that the default location to
serialize the sessions gets blown away during re-deployment and hence
the problem. Work around is to override the default location to a path
which is outside of directories managed by tomcat, e.g.
Context
Manager pathname=/some-path/sessions.ser/
/Context
-Original Message-
From: Aggarwal, Ajay [mailto:ajay.aggar...@stratus.com]
Sent: Wednesday, January 30, 2013 4:52 PM
To: users@tomcat.apache.org
Subject: session persistence across application redeploy
Does session persistence work across application redeploy? I am on
tomcat 7.0.26. And for me session persistence is working across tomcat
restarts, but not when I redeploy my application. I am not using any
special configuration for session persistence (i.e. using the standard
manager).
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
