HI
I was wandering if anyone has experienced similar scenarios.
I have an IIS Web Server which uses JK 1.2 as the connection to the AJP
connector to a jboss 4.01 installation.
The worker.properties are set as follows:
worker.insight.port=8009
worker.insight.type=ajp13
worker.insight.cachesize=768
worker.insight.cache_timeout=60
worker.insight.recycle_timeout=60
worker.insight.socket_keepalive=1
worker.insight.socket_timeout=60
the AJP connector setup is
<Connector port="8009" address="${jboss.bind.address}"
enableLookups="false" redirectPort="8443" debug="0"
minProcessors="75" maxProcessors="200"
acceptCount="1024" connectionTimeout="60000"
protocol="AJP/1.3"/>
After about 5-10 hours of servicing, the AJP connector just builds up
and all 200 connections are used, and doesn't seem to fulfil the
response. When I monitor this using the web-console, all the ajp
connections are used up with the same url, and seems to hang.
Has anyone seen a similar scenario.
Cheers
Steve
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
