Hi!
First, I must say that I found in the archives the exact problem I have
now, but no solution was presented.
My application (built using Apache Wicket), is stateful. When I reload
it, or when I restart Tomcat, the session is correctly serialized and
restored. Jetty is also able to restore sessions. So it's not a problem
of non serializable classes stored in the session.
The problem is when I redeploy the application, no mater how I do it
(replacing war, with lambda probe or with tomcat redeployer). Even if
the war was not changed, the session is destroyed.
We need to change and redeploy the application during production hours.
We can't do that breaking all users sessions. Is there a way to do that?
Adriano
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
