DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22716>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22716 NotSerializableException not caught by PersistentManager Summary: NotSerializableException not caught by PersistentManager Product: Tomcat 4 Version: 4.1.24 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When we change classes in our webapps that uses persistent sessions, the older sessions throw NotSerializableExceptions (because the class changed). This causes a couple of problems. First, the thread that checks for timeouts (PersistentManagerBase.run()) exits. Second, if we try to get a session that contains objects of the old (unserializable) class then it returns a "valid" session with nothing in it (shouldn't it be invalidated?). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
