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=42926>. 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=42926 Summary: Problem with standard path for SESSIONS.ser Product: Tomcat 5 Version: 5.5.23 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] According to Tomcat's documentation, the standard manager implementation (StandardManager) serializes session data on Tomcat shutdown and deserializes the data on Tomcat startup. This works fine. The documentation also states that the same should happen when a context is reloaded. The standard session file is "SESSIONS.ser" in the context's work directory. When a context is reloaded, however, Tomcat serializes the session data correctly, but since the session data file is in the work directory by default and tomcat deletes that directory's contents on context reloading, the session data file is deleted and cannot be found when it's time to deserialize the session data. Therefore upon context reloading, all sessions are gone. I don't expect this to be a wanted behavior (at least this would require an explicit notice in the documentation). A quick workaround is to specify a session file path outside the work directory. Perhaps by default, the session file should be stored outside the work directory by default or the file should not be deleted upon context reloading. -- 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]
