Apache busy connections - JBOSS Tomcat - Threaddump bottlene
I have already posted this message in another rubric, but i think this is the right topic.
Hello,
I'm using JBoss v4.03 with Apache Web Server for a website which is in a Production state.
I have a strange behavior when i look at the Apache JK Status Manager page. Sometimes i can see a lot of busy connection to tomcat.
I have performed several threaddumps when this happens and yesterday I have noticed a bottle neck which is caused by this thread:
"TP-Processor23222" daemon prio=1 tid=0x3a4ed930 nid=0x61eb runnable [0x0eee8000..0x0eee8e40]
at java.util.TreeMap$3.iterator(TreeMap.java:672)
at java.util.TreeMap.putAll(TreeMap.java:320)
at javax.management.modelmbean.DescriptorSupport.init(DescriptorSupport.java:468)
at javax.management.modelmbean.DescriptorSupport.(DescriptorSupport.java:211)
at javax.management.modelmbean.DescriptorSupport.clone(DescriptorSupport.java:802)
- locked <0x54be3d00> (a javax.management.modelmbean.DescriptorSupport)
at javax.management.modelmbean.ModelMBeanOperationInfo.getDescriptor(ModelMBeanOperationInfo.java:364)
at javax.management.modelmbean.ModelMBeanInfoSupport.getDescriptor(ModelMBeanInfoSupport.java:553)
at org.jboss.mx.modelmbean.ModelMBeanInvoker.override(ModelMBeanInvoker.java:804)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:231)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.server.MBeanServerImpl$3.run(MBeanServerImpl.java:1407)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1402)
at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:361)
at org.apache.commons.modeler.Registry.registerComponent(Registry.java:871)
at org.apache.jk.common.ChannelSocket.registerRequest(ChannelSocket.java:439)
at org.apache.jk.common.HandlerRequest.checkRequest(HandlerRequest.java:459)
- locked <0x597f3458> (a java.lang.Object)
at org.apache.jk.common.HandlerRequest.decodeRequest(HandlerRequest.java:470)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:363)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:748)
at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:678)
at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:871)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
at java.lang.Thread.run(Thread.java:595)
Here is the configuration of the connector in /jbossweb-tomcat55.sar/server.xml:
Connector port="11109" address="${jboss.bind.address}"
maxThreads="1000" strategy="ms" minSpareThreads="5" maxSpareThreads="15"
emptySessionPath="true" enableLookups="false" redirectPort="11143"
bufferSize="10240" maxHttpHeaderSize="8192" tcpNoDeal="true"
protocol="AJP/1.3"
Is there a known issue which correspond to this behaviror?
Thanks for your help!