Tomcat Stand-alone

[Carl Olivier <ca...@zero-one.co.za>]

Greetings again all.

Having a very irritating problem.  I am trying to run Tomcat 5.0.25
standalone using 3 HTTP1.1 Coyote connectors - one for "behind the firwall
access", one for standard HTTP requests to all hosts and contexts and 1 for
1 site running HTTPS (SSL) on a specific IP.

Now, when the server starts all goes well up until near the end - where the
following error is thrown in the tomcat logs:

2004/06/18 01:47:32 org.apache.coyote.tomcat5.MapperListener init
WARNING: Error registering contexts
java.util.ConcurrentModificationException
	at java.util.HashMap$HashIterator.nextEntry(HashMap.java:782)
	at java.util.HashMap$EntryIterator.next(HashMap.java:824)
	at java.util.HashMap.putAllForCreate(HashMap.java:424)
	at java.util.HashMap.clone(HashMap.java:656)
	at
mx4j.server.DefaultMBeanRepository.clone(DefaultMBeanRepository.java:56)
	at
mx4j.server.MBeanServerImpl.findMBeansByPattern(MBeanServerImpl.java:1603)
	at
mx4j.server.MBeanServerImpl.queryObjectNames(MBeanServerImpl.java:1568)
	at
mx4j.server.MBeanServerImpl.queryMBeans(MBeanServerImpl.java:1512)
	at
org.apache.coyote.tomcat5.MapperListener.init(MapperListener.java:115)
	at
org.apache.coyote.tomcat5.CoyoteConnector.start(CoyoteConnector.java:1510)
	at
org.apache.catalina.core.StandardService.start(StandardService.java:485)
	at
org.apache.catalina.core.StandardServer.start(StandardServer.java:2298)
	at org.apache.catalina.startup.Catalina.start(Catalina.java:556)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
	at java.lang.reflect.Method.invoke(Method.java:324)
	at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:284)
	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:422)

After this, all 3 the HTTP1.1 Coyote connectors are paused.

This clearly does not help matters.  I read a bugzilla report about a
similar problem in Tomcat 4.1.30 - being fixed, and was wondering if this is
related and would be fixed for TC 5?
(http://issues.apache.org/bugzilla/show_bug.cgi?id=27315)

The funny thing is have another server that is identically setup (same
hardware, software, same TC, same sites/hosts/context) and this does NOT
happen there?

Any assistance would be much appreciated!

Regards,

Carl Olivier

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