-
1. Re: Too many threads being marked as busy in JBoss
starksm64 Aug 28, 2005 2:29 PM (in response to rcostanzo)The keep alive and connection timeout settings are simply keeping a thread dedicated to the ajp requests. Adjust them if you want the connections to be closed after inactivity.
-
2. Re: Too many threads being marked as busy in JBoss
rcostanzo Aug 29, 2005 9:14 AM (in response to rcostanzo)Thanks for the reply. How do I adjust the keep alive and connection timeout settings? Are these configurations for Tomcat or of mod JK?
Here's a snippet from my workers.properties with the timeout configs I've already implemented:
worker.maintain=60
# Define a worker using ajp13
worker.webapp6.port=8009
worker.webapp6.host=mateso-webapp6
worker.webapp6.type=ajp13
worker.webapp6.lbfactor=1
worker.webapp6.disabled=0
worker.webapp6.stopped=0
worker.webapp6.socket_timeout=300
worker.webapp6.recycle_timeout=60
worker.webapp6.reply_timeout=300000 -
3. Re: Too many threads being marked as busy in JBoss
javarako Sep 30, 2005 2:49 PM (in response to rcostanzo)You can adjust the configuration in jboss-3.2.6\server\aProject\deploy\jbossweb-tomcat50.sar\server.xml
Connector port="8788" address="${jboss.bind.address}"
maxThreads="300" minSpareThreads="25" maxSpareThreads="75"
enableLookups="true" redirectPort="8443" acceptCount="100"
connectionTimeout="60000" disableUploadTimeout="true" maxKeepAliveRequests="1"
proxyName="availability.cingular.net" proxyPort="8080" -
4. Re: Too many threads being marked as busy in JBoss
rcostanzo Sep 30, 2005 3:16 PM (in response to rcostanzo)FYI, I just changed Apache from using the prefork MPM to using the worker MPM (and recompiled the mod jk plugin to no use prefork too) and my thread usage counts on JBoss seems accurate. It went way down. I guess there's some issue with Apache/mod-jk prefork which goes away once using the threaded worker MPM.