[jboss-user] [Performance Tuning] - Re: AJP Connector currentThreadCount stays at maximum

normann do-not-reply at jboss.com
Tue Feb 10 05:14:21 EST 2009

My setup has the same issue, which was introduced in the JBoss 4.2 series that upgraded from Tomcat 5.5 to Tomcat 6.

I suspect this has to do with the fact that Tomcat 6 doesn't support the *SpareThreads attributes on the connectors any more. The documentation says that one must define an  element (which defines a thread pool) and reference it in the connector.

In my opinion, your case should be configured like this:

<Executor name="default" minSpareThreads="5" maxThreads="256" />
  | <Connector port="8009" address="${jboss.bind.address}" protocol="AJP/1.3"
  |     emptySessionPath="true" enableLookups="false" redirectPort="8443"
  |     connectionTimeout="20000" executor="default" />

It you use other connectors as well, they might want to reference the executor as well. It seems that it's not possible to set maxSpareThreads any more.

I've tried fiddling with this in my own setup, but I end up in a situation where mod_jk ends up writing to closed Tomcat sockets which result in requests that lock until mod_jk times out. At this point, though, I don't have the time to look more into the matter.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208440#4208440

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208440

More information about the jboss-user mailing list