On Jul 14, 2004, at 11:32 AM, Nick Heudecker wrote:
Another way to solve this is to tell Tomcat not to serialize the
session data when shutting down. Granted, this may not be optimal for
your particular environment, especially for a hot redeploy.
I made it a FAQ: http://www.hibernate.org/212.htm
Another way to solve this is to tell Tomcat not to serialize the session
data when shutting down. Granted, this may not be optimal for your
particular environment, especially for a hot redeploy.
Here's how you do it:
The Manager element does the trick. This has been tested with Tomcat
On Jul 14, 2004, at 10:18 AM, Gavin King wrote:
AFAICT, it should be the application's responsibility to ensure that
it bootstraps Hibernate *before* the session is deserialized.
Then the lookup would be successful.
But this means that a new SessionFactory with a new UUID will be
created and the
We have problem with "SessionFactory not found: null" messages when
Tomcat reloads a servlet context. This happens when you have a
disconnected Session in your HttpSession, which is then
serialized/deserialized while the classloader is restarted. This breaks
the internals of Hibernate, as Hiber
Ah. True.
Christian Bauer wrote:
On Jul 14, 2004, at 10:18 AM, Gavin King wrote:
AFAICT, it should be the application's responsibility to ensure that
it bootstraps Hibernate *before* the session is deserialized.
Then the lookup would be successful.
But this means that a new SessionFactory with a
AFAICT, it should be the application's responsibility to ensure that it
bootstraps Hibernate *before* the session is deserialized.
Then the lookup would be successful.
Christian Bauer wrote:
We have problem with "SessionFactory not found: null" messages when
Tomcat reloads a servlet context. Thi
