You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by John Sidney-Woollett <jo...@wardbrook.com> on 2005/01/13 18:50:41 UTC
Error registering RequestProcessor
We're using Tomcat 5.0.28 which is fronted by Apache 1.3.29 + modjk 1.2.6
We're seeing this error message in the logs occasionally. The error
occurs at any time interval AFTER tomcat has been started up - two hours
was the last time it occured after startup.
This server is one of two in a (jk) load balanced configuration - they
do not use or share sessions and act purely as image servers (from a db
+ file system).
13-Jan-2005 17:27:36 org.apache.commons.modeler.Registry registerComponent
SEVERE: Error registering
Catalina:type=RequestProcessor,worker=jk-8009,name=JkRequest129
javax.management.InstanceAlreadyExistsException:
Catalina:type=RequestProcessor,worker=jk-8009,name=JkRequest129
at mx4j.server.MBeanServerImpl.register(MBeanServerImpl.java:1123)
at
mx4j.server.MBeanServerImpl.registerImpl(MBeanServerImpl.java:1054)
at
mx4j.server.MBeanServerImpl.registerMBeanImpl(MBeanServerImpl.java:1002)
at
mx4j.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:978)
at
org.apache.commons.modeler.Registry.registerComponent(Registry.java:871)
at
org.apache.jk.common.ChannelSocket.registerRequest(ChannelSocket.java:436)
at
org.apache.jk.common.HandlerRequest.decodeRequest(HandlerRequest.java:443)
at
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:352)
at
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)
at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:675)
at
org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:534)
13-Jan-2005 17:27:36 org.apache.jk.common.ChannelSocket registerRequest
WARNING: Error registering request
Does anyone know if this is this serious? And do you think that this TC
instance is still able to serve requests. (Because this is our
production environment we can't do much testing with these servers and
haven't seen the error on our development servers).
Thanks for any insight or help.
John Sidney-Woollett
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org