I just noticed something else too, that these messages occur exactly every 15 minutes:
ex: <snip> [Tue Feb 25 17:15:30 2003] [jk_ajp_common.c (626)]: Error connecting to tomcat. Tomcat is probably not started or is listenning on the wrong port. Failed errno = 111 [Tue Feb 25 17:15:30 2003] [jk_ajp_common.c (874)]: Error connecting to the Tomcat process. [Tue Feb 25 17:15:30 2003] [jk_ajp_common.c (1190)]: sending request to tomcat failed in send loop. err=1 [Tue Feb 25 17:15:30 2003] [jk_connect.c (203)]: jk_open_socket, connect() failed errno = 111 [Tue Feb 25 17:15:30 2003] [jk_ajp_common.c (626)]: Error connecting to tomcat. Tomcat is probably not started or is listenning on the wrong port. Failed errno = 111 [Tue Feb 25 17:15:30 2003] [jk_ajp_common.c (874)]: Error connecting to the Tomcat process. [Tue Feb 25 17:15:30 2003] [jk_ajp_common.c (1190)]: sending request to tomcat failed in send loop. err=2 [Tue Feb 25 17:15:30 2003] [jk_ajp_common.c (1198)]: Error connecting to tomcat. Tomcat is probably not started or is listenning on the wrong port. Failed errno = 111 [Tue Feb 25 17:30:26 2003] [jk_ajp_common.c (681)]: ERROR: can't receive the response message from tomcat, network problems or tomcat is down. [Tue Feb 25 17:30:26 2003] [jk_ajp_common.c (1050)]: Error reading reply from tomcat. Tomcat is down or network problems. [Tue Feb 25 17:30:26 2003] [jk_ajp_common.c (1187)]: ERROR: Receiving from tomcat failed, recoverable operation. err=0 [Tue Feb 25 17:30:26 2003] [jk_connect.c (203)]: jk_open_socket, connect() failed errno = 111 [Tue Feb 25 17:30:26 2003] [jk_ajp_common.c (626)]: Error connecting to tomcat. Tomcat is probably not started or is listenning on the wrong port. Failed errno = 111 [Tue Feb 25 17:30:26 2003] [jk_ajp_common.c (874)]: Error connecting to the Tomcat process. [Tue Feb 25 17:30:26 2003] [jk_ajp_common.c (1190)]: sending request to tomcat failed in send loop. err=1 [Tue Feb 25 17:30:26 2003] [jk_connect.c (203)]: jk_open_socket, connect() failed errno = 111 [Tue Feb 25 17:30:26 2003] [jk_ajp_common.c (626)]: Error connecting to tomcat. Tomcat is probably not started or is listenning on the wrong port. Failed errno = 111 [Tue Feb 25 17:30:26 2003] [jk_ajp_common.c (874)]: Error connecting to the Tomcat process. [Tue Feb 25 17:30:26 2003] [jk_ajp_common.c (1190)]: sending request to tomcat failed in send loop. err=2 [Tue Feb 25 17:30:26 2003] [jk_ajp_common.c (1198)]: Error connecting to tomcat. Tomcat is probably not started or is listenning on the wrong port. Failed errno = 111 [Tue Feb 25 17:30:26 2003] [jk_connect.c (203)]: jk_open_socket, connect() failed errno = 111 [Tue Feb 25 17:30:26 2003] [jk_ajp_common.c (626)]: Error connecting to tomcat. Tomcat is probably not started or is listenning on the wrong port. Failed errno = 111 [Tue Feb 25 17:30:26 2003] [jk_ajp_common.c (874)]: Error connecting to the Tomcat process. [Tue Feb 25 17:30:26 2003] [jk_ajp_common.c (1190)]: sending request to tomcat failed in send loop. err=0 [Tue Feb 25 17:30:26 2003] [jk_connect.c (203)]: jk_open_socket, connect() failed errno = 111 <snip> [Tue Feb 25 17:30:42 2003] [jk_connect.c (203)]: jk_open_socket, connect() failed errno = 111 [Tue Feb 25 17:30:42 2003] [jk_ajp_common.c (626)]: Error connecting to tomcat. Tomcat is probably not started or is listenning on the wrong port. Failed errno = 111 [Tue Feb 25 17:30:42 2003] [jk_ajp_common.c (874)]: Error connecting to the Tomcat process. [Tue Feb 25 17:30:42 2003] [jk_ajp_common.c (1190)]: sending request to tomcat failed in send loop. err=2 [Tue Feb 25 17:30:42 2003] [jk_ajp_common.c (1198)]: Error connecting to tomcat. Tomcat is probably not started or is listenning on the wrong port. Failed errno = 111 [Tue Feb 25 17:45:26 2003] [jk_ajp_common.c (681)]: ERROR: can't receive the response message from tomcat, network problems or tomcat is down. [Tue Feb 25 17:45:26 2003] [jk_ajp_common.c (1050)]: Error reading reply from tomcat. Tomcat is down or network problems. [Tue Feb 25 17:45:26 2003] [jk_ajp_common.c (1187)]: ERROR: Receiving from tomcat failed, recoverable operation. err=0 [Tue Feb 25 17:45:26 2003] [jk_connect.c (203)]: jk_open_socket, connect() failed errno = 111 [Tue Feb 25 17:45:26 2003] [jk_ajp_common.c (626)]: Error connecting to tomcat. Tomcat is probably not started or is listenning on the wrong port. Failed errno = 111 [Tue Feb 25 17:45:26 2003] [jk_ajp_common.c (874)]: Error connecting to the Tomcat process. [Tue Feb 25 17:45:26 2003] [jk_ajp_common.c (1190)]: sending request to tomcat failed in send loop. err=1 Travis ---- Original Message ---- From: [EMAIL PROTECTED] Sent: 2003-02-25 To: Tomcat Developers List <[EMAIL PROTECTED]> Subject: RE: socket errors in catalina.out and mod_jk.log I am getting the exact same messages as of upgrading from 3.2.3 to 4.1.18 yesterday. Travis ---- Original Message ---- From: =?UTF-8?B?U3ZlbiBLw7ZobGVy?= <[EMAIL PROTECTED]> Sent: 2003-02-25 To: [EMAIL PROTECTED] Subject: socket errors in catalina.out and mod_jk.log hi, i didn't get any useful response in the tomcat-user-mailinglist. many users have messages in their catalina.out, saying that a socket times out, or a connection had been closed. these messages look like this: 25.02.2003 20:22:48 org.apache.jk.common.ChannelSocket processConnection INFO: connection timeout reached 25.02.2003 20:22:50 org.apache.jk.common.ChannelSocket processConnection INFO: server has been restarted or reset this connection these messages appear frequently (about every second) the first message occurs more often than the second one. i know now, that the second message appears, if apache closes it socket, and tomcat get a read-error or such. i don't know, why the first message appears. would be nice to know! in addition, i see many errors in mod_jk's error-log, if i set the log-level to "error". WHY (and i have asked myself a thousand times) is this? - why doesn't mod_jk send a quit-command to tomcat, and both sides will gracefully close the connection? - why do the connections timeout? why isn't there something like a keep-alive which is send my mod_jk every now and than? does the AJP13 protocol include keep-alives? does it include something like quit-command? if not (that would be a shame btw) is this included in AJP14? is this a known, but still not fixed, problem? why isn't it fixed? i cannot understand, how you can live with that!? it might be my fault, but nobody seems to know anything about these strange messages! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
