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=40811>. 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=40811 Summary: Context listeners called multiple times Product: Tomcat 5 Version: 5.5.20 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: Unknown AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] In web.xml, if I define a listener-class, the contextInitialized method in this class is called twice when Tomcat starts up (startup.sh). In both cases the context being initialized is the same - and in my case there is only one context. This clearly is not correct behaviour. Tomcat should only invoke the contextInitialized method once for each context being initialized. I have tried to use static class members to flag my context as having already been initialized, but this does not work. It seems as if two independant class loaders are loading my listener, because they do not share static class variables. I'm sure whoever reads this will need some information about the environment. It's basically a really simple Fedora Core 5 setup with Tomcat 5.5.20 running and mod_jk integration to Apache. Tomcat works fine once it is running - it just breaks my webapp that the listener class is executed twice. What can I do to work around this if indeed it is a bug? -- 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]
