I only added socket_timeout in after looking at the included file in 1.2.30. I was hoping that there was something in that file that I was missing.
I attached the log files that you asked for. Looking through them, I don't see any notable increases in response times. This is a system that is not (yet) actively used, so there is very little load. The thread dumps and the gc log do not seem to indicate that tomcat is pausing in some meaningful way. Also, during this time period, the http connectors in the tomcat instances are responding without delay (hitting the manager page). Another detail is that bouncing tomcat will clear up this problem for some unknown period of time. Here is the worker.properties file: ******************************* # Define 1 real worker using ajp13 worker.list=lb,jkstatus,cas # Set properties for worker1 (ajp13) worker.template.type=ajp13 worker.template.retries=4 worker.template.lbfactor=1 worker.template.reply_timeout=300000 worker.template.max_reply_timeouts=10 worker.template.connection_pool_timeout=60 worker.template.connection_pool_minsize=0 worker.template.ping_mode=A worker.template.ping_timeout=10000 #worker.template.socket_timeout=10 worker.template.socket_keepalive=true worker.template.socket_connect_timeout=10000 worker.tomcat01-instance1.reference=worker.template worker.tomcat01-instance1.host=tomcat01.barnhardt.local worker.tomcat01-instance1.port=8009 worker.tomcat01-instance2.reference=worker.template worker.tomcat01-instance2.host=tomcat01.barnhardt.local worker.tomcat01-instance2.port=18009 worker.tomcat02-instance1.reference=worker.template worker.tomcat02-instance1.host=tomcat02.barnhardt.local worker.tomcat02-instance1.port=8009 worker.tomcat02-instance2.reference=worker.template worker.tomcat02-instance2.host=tomcat02.barnhardt.local worker.tomcat02-instance2.port=18009 worker.cas.type=ajp13 worker.cas.host=localhost worker.cas.port=8009 worker.cas.lbfactor=1 worker.cas.connection_pool_timeout=600 worker.cas.socket_keepalive=1 worker.cas.socket_timeout=60 # Set properties for lb which use the other workers worker.lb.type=lb #worker.lb.method=B worker.lb.sticky_session=True worker.lb.balance_workers=tomcat01-instance1,tomcat01-instance2,tomcat02-instance1,tomcat02-instance2 # Define a 'jkstatus' worker using status worker.jkstatus.type=status ************************ Any thoughts? Thanx for the time, LES LES wrote: > > Ok, let me see if I can correlate the various logs and I will post them > later today. Thanx for the help. > > LES > > Rainer Jung-3 wrote: >> >> On 11.06.2010 16:28, LES wrote: >>> >>> Well, your suggested changes worked...until today. It was absolutely >>> rock >>> solid. Then, the last two days, with no load I started receiving >>> errno=110 >>> again. It didn't last all day, only a couple of hours yesterday and a >>> couple today. I have added a socket timeout and am trying to track down >>> any >>> issues on the tomcat side that could have contributed. Any idea where I >>> should look?? >> >> 1) I'm not a big fan of "socket_timeout". It can do more harm than good. >> >> 2) "where should I look": Errno 110 is a timeout, so maybe mod_jk just >> does what you told it to: timing out. Why? There might be a problem on >> the backend (performance problem, thread deadlocks or similar). Activate >> an access log on the backend (Tomcat) and add "%D" to the log pattern >> which will give you millisecond response times for Tomcat. Then it's >> easier to check, whether responses get slow. You can also monito the >> "busy" counts in the jk status worker display. >> >> Finally: Look at the mod_jk log file or provide it for us. >> >> Regards, >> >> Rainer >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> >> > > http://old.nabble.com/file/p28858465/modjk_log_files.tar.gz modjk_log_files.tar.gz -- View this message in context: http://old.nabble.com/mod_jk-stability-issues-tp28662097p28858465.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
