Re: Bug? Repost: JkCoyoteHandler Error
This is the same bug as the memory leak bug that has been going on and on and on and on this list ;-). The fix is the same: 1) Use the work-around of setting 'request.registerRequests=false' in jk2.properties. 2) Upgrade to 5.0.20+ Allistair Crossley [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hi All, This is a repost of an issue we are still experiencing on the production server. I found a similar post re: tomcat 4 that was a bug (although cannot find in bugzilla now). The same thing happens to us .. I have been looking through our production server logs and the following error block is repeated an awful lot, like every 6 minutes or so and sometimes 6 times per minute. 06-May-2004 14:38:50 org.apache.jk.server.JkCoyoteHandler action SEVERE: Error in action code java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:489) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:697) at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:487) at org.apache.coyote.Response.action(Response.java:226) at org.apache.coyote.Response.finish(Response.java:348) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:344) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:415) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:716) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:650) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:829) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:688) at java.lang.Thread.run(Thread.java:534) 06-May-2004 14:38:50 org.apache.jk.common.HandlerRequest invoke INFO: Unknown message 0 The difficult part is that no user has reported any errors to us and I have never seen an error arise from using the system, so I am a little puzzled at where this is coming from and despite not having errors reveal themselves or being reported, I still want to get to the bottom of them and remove the cause if possible. The system is now fairly basic: IIS + NTLM Auth -- JK2 -- Tomcat 5.0.19 If anyone could suggest what this error may be, why I may be getting it or how I can go about getting better resolution on the root cause I would be very grateful, Cheers, Allistair. The post I found on Google is as follows but the 2 bugs listed below are no longer there... http://nagoya.apache.org/bugzilla/show_bug.cgi?idW35 http://nagoya.apache.org/bugzilla/show_bug.cgi?idF63 -Original Message- From: Boemio, Neil (IT, FGIC) [mailto:Neil.Boemio@(protected)] Sent: 07 ßíóàðè 2004 ?. 22:16 To: Tomcat Users List Subject: Tomcat: Connection reset by peer: socket write error My W2K, Apache 2.0.47, Tomcat 4.1.27, JK2 2.0.43 setup works fine . for a while. After an hour, a few hours, maybe minutes (I don 't really see a pattern), my JSP pages will hang. When I restart the Tomcat service, everything is fine again until the next hang. Here 's the sequence: About every minute in the jk2.log, I get this set or errors over and over again. This doesn 't seem to be directly related to my problem because this happens even when everything is OK but I thought I would include it as well: [Wed Jan 07 14:19:27 2004] (error ) [jk_channel_socket.c (557)] channelSocket.receive(): Error receiving message body -1 0 [Wed Jan 07 14:19:27 2004] (error ) [jk_workerEnv.c (482)] workerEnv.processCallbacks() Error reading reply [Wed Jan 07 14:19:27 2004] (error ) [jk_worker_ajp13.c (416)] ajp13.service() ajpGetReply recoverable error 12 [Wed Jan 07 14:19:49 2004] (error ) [jk_channel_socket.c (557)] channelSocket.receive(): Error receiving message body -1 0 [Wed Jan 07 14:19:49 2004] (error ) [jk_workerEnv.c (482)] workerEnv.processCallbacks() Error reading reply [Wed Jan 07 14:19:49 2004] (error ) [jk_worker_ajp13.c (416)] ajp13.service() ajpGetReply recoverable error 12 When the problem occurs, I get this in the Tomcat Error Log: Jan 7, 2004 2:21:25 PM org.apache.jk.server.JkCoyoteHandler action SEVERE: Error in action code java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(Unknown Source) at java.net.SocketOutputStream.write(Unknown Source) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:407) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:599) at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:385) at
Bug? Repost: JkCoyoteHandler Error
Hi All, This is a repost of an issue we are still experiencing on the production server. I found a similar post re: tomcat 4 that was a bug (although cannot find in bugzilla now). The same thing happens to us .. I have been looking through our production server logs and the following error block is repeated an awful lot, like every 6 minutes or so and sometimes 6 times per minute. 06-May-2004 14:38:50 org.apache.jk.server.JkCoyoteHandler action SEVERE: Error in action code java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:489) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:697) at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:487) at org.apache.coyote.Response.action(Response.java:226) at org.apache.coyote.Response.finish(Response.java:348) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:344) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:415) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:716) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:650) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:829) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:688) at java.lang.Thread.run(Thread.java:534) 06-May-2004 14:38:50 org.apache.jk.common.HandlerRequest invoke INFO: Unknown message 0 The difficult part is that no user has reported any errors to us and I have never seen an error arise from using the system, so I am a little puzzled at where this is coming from and despite not having errors reveal themselves or being reported, I still want to get to the bottom of them and remove the cause if possible. The system is now fairly basic: IIS + NTLM Auth -- JK2 -- Tomcat 5.0.19 If anyone could suggest what this error may be, why I may be getting it or how I can go about getting better resolution on the root cause I would be very grateful, Cheers, Allistair. The post I found on Google is as follows but the 2 bugs listed below are no longer there... http://nagoya.apache.org/bugzilla/show_bug.cgi?idW35 http://nagoya.apache.org/bugzilla/show_bug.cgi?idF63 -Original Message- From: Boemio, Neil (IT, FGIC) [mailto:Neil.Boemio@(protected)] Sent: 07 ßíóàðè 2004 ?. 22:16 To: Tomcat Users List Subject: Tomcat: Connection reset by peer: socket write error My W2K, Apache 2.0.47, Tomcat 4.1.27, JK2 2.0.43 setup works fine . for a while. After an hour, a few hours, maybe minutes (I don 't really see a pattern), my JSP pages will hang. When I restart the Tomcat service, everything is fine again until the next hang. Here 's the sequence: About every minute in the jk2.log, I get this set or errors over and over again. This doesn 't seem to be directly related to my problem because this happens even when everything is OK but I thought I would include it as well: [Wed Jan 07 14:19:27 2004] (error ) [jk_channel_socket.c (557)] channelSocket.receive(): Error receiving message body -1 0 [Wed Jan 07 14:19:27 2004] (error ) [jk_workerEnv.c (482)] workerEnv.processCallbacks() Error reading reply [Wed Jan 07 14:19:27 2004] (error ) [jk_worker_ajp13.c (416)] ajp13.service() ajpGetReply recoverable error 12 [Wed Jan 07 14:19:49 2004] (error ) [jk_channel_socket.c (557)] channelSocket.receive(): Error receiving message body -1 0 [Wed Jan 07 14:19:49 2004] (error ) [jk_workerEnv.c (482)] workerEnv.processCallbacks() Error reading reply [Wed Jan 07 14:19:49 2004] (error ) [jk_worker_ajp13.c (416)] ajp13.service() ajpGetReply recoverable error 12 When the problem occurs, I get this in the Tomcat Error Log: Jan 7, 2004 2:21:25 PM org.apache.jk.server.JkCoyoteHandler action SEVERE: Error in action code java.net.SocketException: Connection reset by peer: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(Unknown Source) at java.net.SocketOutputStream.write(Unknown Source) at org.apache.jk.common.ChannelSocket.send(ChannelSocket.java:407) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:599) at org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler.java:385) at org.apache.coyote.Response.action(Response.java:222) at org.apache.coyote.Response.finish(Response.java:343) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:268) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at
