DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=26372>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=26372 ------- Additional Comments From [EMAIL PROTECTED] 2006-01-25 17:09 ------- For your information, I've tracked down at least one underlying cause of this kind of failure. During shutdown, Tomcat tries to serialize HTTP sessions to disk. If a session contains Hibernate objects associated with a hibernate session which has already been closed, then object.writeReplace() will throw an exception. This, in turn, causes the serialization process to failure and Tomcat's reload operation fails as well. I'd expect Tomcat to be more robust. Specifically, it should emit a warning that "serialization on shutdown" has failed but should not fail the overall reload operation. Secondly, if an exception is thrown during serialization it should print out the stack-trace, not just the exception message (which is what it does now). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
