tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Armintor" <>
Subject RE: significance of and tomcat log messages?
Date Wed, 28 Apr 2004 15:59:05 GMT
Are the jk2 worker sockets also timing out after 4 seconds? If not, you
may be seeing those messages when jk2 is still using a socket that
Tomcat has timed out.  The stop button message, by the by, refers to a
broken pipe.

Benjamin J. Armintor
Systems Analyst
ITS-Systems: Mainframe Group
University of Texas - Austin
tele: (512) 232-6562

-----Original Message-----
From: [] 
Sent: Wednesday, April 28, 2004 10:27 AM
Subject: significance of and tomcat log messages?

We are running a commercial webapp on Apache2 (2.0.49)->
(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
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

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message