Problem: The communication via mod_jk between Apache and Tomcat appears to suddenly become "exhausted" and cease to be available.

Versions:

apache-tomcat-5.5.23.tar.gz
httpd-2.0.59.tar.gz
tomcat-connectors-1.2.21-src.tar.gz
managerx-5.5-1.7.2
CentOS 4.6 (final)

Symptom:

Apache suddenly reports that the "service is unavailable" when trying to serve a context from Tomcat.

Frequency:

Generally about once a month. It also can happen quicker if ManagerX is used with any frequency. I have about 10 different webapps running. Restarting Tomcat does nothing, Restarting both Apache and Tomcat does nothing.. ONLY rebooting the machine will get everything back working.

Possibly related information:

netstat -np --tcp reports dozens of "dead" connections to port 8009, like the following samples: (count in parens to save space here):

tcp 0 0 127.0.0.1:8009 127.0.0.1:48461 SYN_RECV - (13) tcp 0 6 127.0.0.1:48459 127.0.0.1:8009 FIN_WAIT1 - (3) tcp 6 0 ::ffff:127.0.0.1:8009 ::ffff:127.0.0.1:48191 CLOSE_WAIT - (50)

and NO established connections even when attempting to access a service on Tomcat

I attempted to work on various settings in the worker.properties file under the assumption that this is the key area to try and solve the problem based on a number of messages here and at other venues. I'm assuming I still do not have it right, but have exhausted my understanding of the causes..

worker.properties:

worker.list=ajp13
worker.ajp13.port=8009
worker.ajp13.host=localhost
worker.ajp13.type=ajp13
worker.ajp13.cachesize=30
worker.ajp13.socket_timeout=120
worker.ajp13.connection_pool_timeout=600
worker.ajp13.connect_timeout=7000
worker.ajp13.prepost_timeout=7000
worker.ajp13.reply_timeout=60000
worker.ajp13.recycle_timeout=120
worker.ajp13.retries=3

Anyone have some suggestions as to how to solve this problem.. It is rendering my production machines nearly useless..

Thank You!

John..


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to