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=5852>. 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=5852 SessionCreated called twice Summary: SessionCreated called twice Product: Tomcat 4 Version: 4.0.1 Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When shutting down Tomcat, the sequence of events for the listeners is as such, assuming you have one attribute in one session : - sessionWillPassivate (ok) - valueUnbound (ok) - attributeRemoved (ok) - sessionCreated (?) - sessionCreated (once again) - contextDestroyed (ok) Why is it necessary to call sessionCreated ? Why twice ? Also when Tomcat starts, it never produces SessionDidActivate() events. Thank you all for your hard work ! JFH -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
