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=39866>. 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=39866 Summary: Context manager name isn't reset correctly after reload, in a cluster. Product: Tomcat 5 Version: 5.5.17 Platform: Other OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: Catalina:Cluster AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] The context manager name refered to by the cluster doesn't appear to be reset when the context reloads. Other nodes in the cluster receive messages with an incorrect manager name, after a distributable context is updated by adding or updating a jar or the web.xml file. The name appears to be appended to it's previous value after each reload. Other members of the cluster log messages from the updated node as follows: SEVERE: Context manager doesn't exist:host1host1 SEVERE: Context manager doesn't exist:host1host1host1 (In our case there was only a root context in each host.) The Cluster definition is exactly as it is in the default server.xml, except that it's placed at the Engine level, rather than inside a Host. -- 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]
