I was wondering if anyone has encountered the following problem with Coyote JK Connector. We have recently switched from deprecated JK connector, to Coyote JK connector on Tomcat side. We're using Tomcat
4.1.27 with Apache 1.3.29. Apache side has been running mod_jk 1.2.x before and after the switch. After the switch was made, catalina.out constantly gets the following errors - every few seconds in fact.
Dec 12, 2003 1:08:22 PM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Dec 12, 2003 1:08:40 PM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Dec 12, 2003 1:08:43 PM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Dec 12, 2003 1:08:58 PM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Dec 12, 2003 1:09:01 PM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection Dec 12, 2003 1:09:08 PM org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection
Because of that, the file has been growing fairly rapidly. I found the discussion of these errors in the tomcat-dev mailing list a while ago, and the consensus seemed to be that they are harmless, caused by the restarts of Apache processes and the severity of the error should really be changed to DEBUG from INFO. Is this in fact the case, and are there still plans to in fact change the severity of those messages? Until this is done - is there a way to make them disappear, preventing the log file from growing rapidly?
Thanks in advance, -M-
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
