tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From S...@nisource.com
Subject significance of mod_jk2.so and tomcat log messages?
Date Wed, 28 Apr 2004 15:26:42 GMT
We are running a commercial webapp on Apache2 (2.0.49)->mod_jk2.so
(2.0.49)-> tomcat 4.1.27 on win2k server sp4, Sun 1.4.2_02 sdk.

I am seeing many of the following messages logged:

In apache2 error.log:
[Tue Apr 27 18:41:17 2004] [error] workerEnv.processCallbacks() Error
reading reply
[Tue Apr 27 18:41:17 2004] [error] ajp13.service() ajpGetReply recoverable
error 120000

In tomcat error log:
Apr 27, 2004 6:42:31 PM org.apache.jk.common.ChannelSocket
processConnection
INFO: connection timeout reached

Currently our tomcat settings are acceptCount="500"
connectionTimeout="4000". If I decrease the connectionTimeout setting I see
more of the above tomcat messages, which makes sense. The vendor does not
recommend increasing the value beyond 4000. The value of 4000 was set
empirically during our load testing process.

Can anyone share the significance (or not) of these or point me at the
appropriate docs? From reviewing the list archive, I suspect that the
mod_jk2 message is normal when a user hits the stop button in their browser
(broken pipe) and the tomcat message is also normal, but am looking for
confirmation.

Stephan Noe
snoe@nisource.com




---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Mime
View raw message