a) Use a newer tomcat release 5.0.30 better 5.5.9 or higher
b) <5.0.30 has a memory leak with registering stats as jk requests
use request.registerRequests=false inside you worker2.properties
Peter
Laurent Perez schrieb:
Hello
I'm using Apache2 + mod_jk + Tomcat 5.0.25 for a customer web site,
everything seems to work ok, but under heavy load, the following error
randomly appears inside my catalina.out :
12 déc. 2005 14:46:53 org.apache.commons.modeler.Registry registerComponent
FATAL: Error registering
Catalina:type=RequestProcessor,worker=jk-8009,name=JkRequest39683
javax.management.InstanceAlreadyExistsException:
Catalina:type=RequestProcessor,worker=jk-8009,name=JkRequest39683
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)
12 déc. 2005 14:46:53 org.apache.jk.common.ChannelSocket registerRequest
ATTENTION: Error registering request
I'm puzzled with this "InstanceAlreadyExistsException" exception,
because I'm only using one Tomcat instance, with one worker.
After this error happens, the site is still running, but performance
is slowly degrading, too many tomcat threads - I presume one for every
mod_jk request - are created and do not seem to be cleanup up, the cpu
slowly raises to 100%, and a few hours later I have to restart Tomcat
because every request goes timeout.
Is it a known performance problem and are there tips to avoid this ?
Thanks for any input
Laurent
--
<a href="http://in-pocket.blogspot.com";>http://in-pocket.blogspot.com
- Mobile world, technology and more</a>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
