DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16357>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16357 "connection timeout reached" in logs when using apache/jk Summary: "connection timeout reached" in logs when using apache/jk Product: Tomcat 4 Version: 4.1.18 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Connector:Coyote JK 2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] In the tomcat log I find a lot of: 23-Jan-2003 11:08:43 org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached Here's an email that explains it: > -----Original Message----- > From: Hannu Kivimäki [mailto:[EMAIL PROTECTED]] > Sent: 23 January 2003 11:20 > To: [EMAIL PROTECTED] > Subject: Re: strange messages in tomcat 4.1.18 > This has been discussed briefly before, see > http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg38339.html > If you are using Apache (1.3.x, don't know about 2.0.x) as web server, this > message simply means that an Apache child process was restarted. And yes, > > these are non-harmful messages. See http://httpd.apache.org/docs/mod/core.html#maxrequestsperchild > if you'd like to change the restart frequency (there's probably no need to). > To prevent messages from showing up in catalina.out you need to adjust logging level for org.apache.jk.common.ChannelSocket. AFAIK this cannot be done by altering log settings in server.xml. Instead, add line > org.apache.jk.common.ChannelSocket.level = WARNING > to the end of logging.properties in JRE 1.4.x's lib directory (by default /usr/java/jre/lib in Solaris, /usr/java/j2sdk1.4.x/jre/lib in Linux). > If you don't want to mess around with default logging file, you can make a copy of it and add parameter > -Djava.util.logging.config.file=somefile > into Tomcat startup script. > I'd vote for changing log level of these "server has been restarted..." messages from INFO to DEBUG in next Tomcat release. There's enough settings to > do even without tampering JRE's property files. :) > Hannu -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
