You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2004/10/28 18:00:45 UTC

DO NOT REPLY [Bug 31940] New: - Setting the context as reloadable='true' doesn't fire a sessionCreated event

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=31940>.
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=31940

Setting the context as reloadable='true' doesn't fire a sessionCreated event

           Summary: Setting the context as reloadable='true' doesn't fire a
                    sessionCreated event
           Product: Tomcat 5
           Version: 5.0.28
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: mattia.dongili@siemens.com


As per subject. The problem is that I'm trying to track sessions (Italian 
privacy laws) and while developing I have the context where I deploy my 
application set as reloadable='true'. So far so good.
The problem is that when the context is reloaded, sessions are kept but no 
sessionCreated event is fired (and no attributeAdded event either) while 
contextInitialized events are fired.

I believe this is a bug in Tomcat.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org