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
