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=30771>. 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=30771 Error registering contexts; with multiple services on fast box Summary: Error registering contexts; with multiple services on fast box Product: Tomcat 5 Version: 5.0.27 Platform: Other OS/Version: FreeBSD Status: NEW Severity: Normal Priority: Other Component: Connector:Coyote AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The attached server.xml has 5 <service> defined, each with its own Connector, Engine and Host. I get a ConcurrentModificationException fault when starting Tomcat that breaks the context registration. The stack trace is shown in the attached cataline.out. My feeling is that this issue only occurs on a fast machine which is registering a whole series of services and there is unthread-safe code somewhere in the CoyoteConnector code or the underlying MBean system. I used the server-minimal.xml model to originate my server.xml (e.g. having <Connector port="8013" />) but I found that including more attributes to that Connector entity (the standard attributes suggested in the default server.xml) caused the Error registering contexts fault to go away. This workaround does not work on the reproducible case I have prepared; my hunch is that this fault is highly time dependent - as I think it must a threading issues. My environment: FreeBSD 5.2.1 JDK 1.4.2 (patched for FreeBSD) Tomcat 5.0.27 Hardware: AMD Athlon XP 2800+, RAM 447MB Reproducible Case Do these things on a clean tomcat install: 1. cd <CATALINA_HOME> 2. mkdir -p testsite1/htdocs/WEB-INF 3. cp <a clean web.xml> testsite1/htdocs/WEB-INF 4. cp -r testsite1 testsite2 5. cp -r testsite1 testsite3 6. cp -r testsite1 testsite4 7. cp -r testsite1 testsite5 8. Replace conf/server.xml with the one I have attached to this case. 9. Start Tomcat 10. Inspect the catalina.out The symptom others may find this fault with (if you don't spot the "Error registering contexts" in catalina.out) is that the site that fails will return this HTTP header (which is a consequence of that site not being initialised properly): # curl -I http://localhost:8013/test.jsp HTTP/1.1 400 No Host matches server name localhost Transfer-Encoding: chunked Date: Fri, 20 Aug 2004 11:22:50 GMT Server: Apache-Coyote/1.1 Connection: close --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
