You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Eric Waite <er...@readingplus.com> on 2006/11/14 18:14:55 UTC
SEVERE error in log files
I am receiving the following error in the log files:
Nov 14, 2006 11:32:23 AM org.apache.commons.modeler.Registry
registerComponent
SEVERE: Error registering
Catalina:type=RequestProcessor,worker=jk-8009,name=JkRequest8163016
javax.management.InstanceAlreadyExistsException:
Catalina:type=RequestProcessor,worker=jk-8009,name=JkRequest8163016
at
com.sun.jmx.mbeanserver.RepositorySupport.addMBean(RepositorySupport.java:452)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1410)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:936)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:337)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:497)
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.checkRequest(HandlerRequest.java:454)
at
org.apache.jk.common.HandlerRequest.decodeRequest(HandlerRequest.java:464)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:361)
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:684)
at java.lang.Thread.run(Thread.java:595)
Nov 14, 2006 11:32:23 AM org.apache.jk.common.ChannelSocket registerRequest
WARNING: Error registering request
I am using IIS/Apache Tomcat 5.5.4/AJP1.3 ISAPI plugin
This error appears as load increases on our server, I do not know if it
is load related or not.
I am also not sure if this could be triggered by a client request.
We are trying to isolate an application issue where applets get frozen
and requests never make it to our server,
would or could the error above cause this?
Any help would be appreciated.
Eric
<ma...@tomcat.apache.org>
--
eric@readingplus.com
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org