You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Pete Alvin <pe...@awebabove.com> on 2006/03/09 18:07:43 UTC

Tomcat just died on our Production Server

Any idea what this means?  At 1:52 our Tomcat just stopped serving 
pages.  Help.. my boss is *pissed* and I have no 
idea how to address this.  I re-started Tomcat and I'm back in 
service... but WHY DID IT HAPPEN?

Thanks in advance.  Pete

Mar 9, 2006 1:52:12 AM org.apache.jk.core.MsgContext action
WARNING: Error sending end packet
java.net.SocketException: Broken pipe
        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:508)
        at 
org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:112)
        at org.apache.jk.core.MsgContext.action(MsgContext.java:293)
        at org.apache.coyote.Response.action(Response.java:182)
        at org.apache.coyote.Response.finish(Response.java:304)
        at 
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:204)
        at 
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
        at 
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:744)
        at 
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.jav
a:674)
        at 
org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocke
t.java:866)
        at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPo
ol.java:684)
        at java.lang.Thread.run(Thread.java:534)
Mar 9, 2006 1:52:12 AM org.apache.jk.common.ChannelSocket 
processConnection
WARNING: processCallbacks status 2








---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Tomcat just died on our Production Server

Posted by Mike Sabroff <mi...@cygnusb2b.com>.
This happens to us too, just noticed it in the log today. I will be 
looking into this as we are taking control of our servers in the next 
couple of weeks (currently out-sourcing network admin)

Mike

Tim Lucia wrote:
> Can't this exception be the result of the user hitting the STOP button, or
> simply closing the browser?  I.e., this can happen all the time.  Are you
> certain this is the exact cause of death?
>
> From the stack trace (unless you've filtered it) it appears your code is
> complete, and the response is committed, and that Tomcat is now forwarding
> back through JK to Apache.  So, I'm not sure your application can catch it.
> I.e., you've got no code on the stack which could even have a catch { ... }
> block.
>
> Or am I missing something?
>
> Tim
>
>
> -----Original Message-----
> From: Robert Harper [mailto:robert@iat-cti.com] 
> Sent: Thursday, March 09, 2006 12:19 PM
> To: 'Tomcat Users List'
> Subject: RE: Tomcat just died on our Production Server
>
> It looks like the socket closed for some reason. You might want to try
> catching the exception and doing some clean up so that your app doesn't die.
> The connection is lost but you may be able to recover so that you can keep
> servicing requests from other connections.
>
> One way to test this would be to use your development server to service the
> same requests and while it is busy servicing a request, disconnect the
> network and see what happens to you app. The connection will be dead of
> course but your app should be coded so that it can recover and not need a
> restart so that when the connection is back, your app is ready to service
> more requests.
>
> Robert S. Harper
> Information Access Technology, Inc.
>
> -----Original Message-----
> From: Pete Alvin [mailto:pete@awebabove.com]
> Sent: Thursday, March 09, 2006 10:08 AM
> To: users@tomcat.apache.org
> Subject: Tomcat just died on our Production Server
>
> Any idea what this means?  At 1:52 our Tomcat just stopped serving pages.
> Help.. my boss is *pissed* and I have no idea how to address this.  I
> re-started Tomcat and I'm back in service... but WHY DID IT HAPPEN?
>
> Thanks in advance.  Pete
>
> Mar 9, 2006 1:52:12 AM org.apache.jk.core.MsgContext action
> WARNING: Error sending end packet
> java.net.SocketException: Broken pipe
>         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:508)
>         at
> org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:112)
>         at org.apache.jk.core.MsgContext.action(MsgContext.java:293)
>         at org.apache.coyote.Response.action(Response.java:182)
>         at org.apache.coyote.Response.finish(Response.java:304)
>         at
> org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:204)
>         at
> org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
>         at
> org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:744)
>         at
> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.jav
> a:674)
>         at
> org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocke
> t.java:866)
>         at
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPo
> ol.java:684)
>         at java.lang.Thread.run(Thread.java:534)
> Mar 9, 2006 1:52:12 AM org.apache.jk.common.ChannelSocket
> processConnection
> WARNING: processCallbacks status 2
>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>   

-- 
Mike Sabroff
Web Services
Developer
mike.sabroff@cygnusb2b.com
920-568-8379


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: Tomcat just died on our Production Server

Posted by Robert Harper <ro...@iat-cti.com>.
You are probably right and if that is the case, it should be easy to
reproduce in your testing area and you can work on making your servlet more
bullet proof.

Robert S. Harper
Information Access Technology, Inc.

-----Original Message-----
From: Tim Lucia [mailto:timlucia@yahoo.com] 
Sent: Thursday, March 09, 2006 10:52 AM
To: 'Tomcat Users List'
Subject: RE: Tomcat just died on our Production Server

Can't this exception be the result of the user hitting the STOP button, or
simply closing the browser?  I.e., this can happen all the time.  Are you
certain this is the exact cause of death?

>From the stack trace (unless you've filtered it) it appears your code is
complete, and the response is committed, and that Tomcat is now forwarding
back through JK to Apache.  So, I'm not sure your application can catch it.
I.e., you've got no code on the stack which could even have a catch { ... }
block.

Or am I missing something?

Tim


-----Original Message-----
From: Robert Harper [mailto:robert@iat-cti.com] 
Sent: Thursday, March 09, 2006 12:19 PM
To: 'Tomcat Users List'
Subject: RE: Tomcat just died on our Production Server

It looks like the socket closed for some reason. You might want to try
catching the exception and doing some clean up so that your app doesn't die.
The connection is lost but you may be able to recover so that you can keep
servicing requests from other connections.

One way to test this would be to use your development server to service the
same requests and while it is busy servicing a request, disconnect the
network and see what happens to you app. The connection will be dead of
course but your app should be coded so that it can recover and not need a
restart so that when the connection is back, your app is ready to service
more requests.

Robert S. Harper
Information Access Technology, Inc.

-----Original Message-----
From: Pete Alvin [mailto:pete@awebabove.com]
Sent: Thursday, March 09, 2006 10:08 AM
To: users@tomcat.apache.org
Subject: Tomcat just died on our Production Server

Any idea what this means?  At 1:52 our Tomcat just stopped serving pages.
Help.. my boss is *pissed* and I have no idea how to address this.  I
re-started Tomcat and I'm back in service... but WHY DID IT HAPPEN?

Thanks in advance.  Pete

Mar 9, 2006 1:52:12 AM org.apache.jk.core.MsgContext action
WARNING: Error sending end packet
java.net.SocketException: Broken pipe
        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:508)
        at
org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:112)
        at org.apache.jk.core.MsgContext.action(MsgContext.java:293)
        at org.apache.coyote.Response.action(Response.java:182)
        at org.apache.coyote.Response.finish(Response.java:304)
        at
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:204)
        at
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
        at
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:744)
        at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.jav
a:674)
        at
org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocke
t.java:866)
        at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPo
ol.java:684)
        at java.lang.Thread.run(Thread.java:534)
Mar 9, 2006 1:52:12 AM org.apache.jk.common.ChannelSocket
processConnection
WARNING: processCallbacks status 2








---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org





---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org





---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: Tomcat just died on our Production Server

Posted by Tim Lucia <ti...@yahoo.com>.
Can't this exception be the result of the user hitting the STOP button, or
simply closing the browser?  I.e., this can happen all the time.  Are you
certain this is the exact cause of death?

>From the stack trace (unless you've filtered it) it appears your code is
complete, and the response is committed, and that Tomcat is now forwarding
back through JK to Apache.  So, I'm not sure your application can catch it.
I.e., you've got no code on the stack which could even have a catch { ... }
block.

Or am I missing something?

Tim


-----Original Message-----
From: Robert Harper [mailto:robert@iat-cti.com] 
Sent: Thursday, March 09, 2006 12:19 PM
To: 'Tomcat Users List'
Subject: RE: Tomcat just died on our Production Server

It looks like the socket closed for some reason. You might want to try
catching the exception and doing some clean up so that your app doesn't die.
The connection is lost but you may be able to recover so that you can keep
servicing requests from other connections.

One way to test this would be to use your development server to service the
same requests and while it is busy servicing a request, disconnect the
network and see what happens to you app. The connection will be dead of
course but your app should be coded so that it can recover and not need a
restart so that when the connection is back, your app is ready to service
more requests.

Robert S. Harper
Information Access Technology, Inc.

-----Original Message-----
From: Pete Alvin [mailto:pete@awebabove.com]
Sent: Thursday, March 09, 2006 10:08 AM
To: users@tomcat.apache.org
Subject: Tomcat just died on our Production Server

Any idea what this means?  At 1:52 our Tomcat just stopped serving pages.
Help.. my boss is *pissed* and I have no idea how to address this.  I
re-started Tomcat and I'm back in service... but WHY DID IT HAPPEN?

Thanks in advance.  Pete

Mar 9, 2006 1:52:12 AM org.apache.jk.core.MsgContext action
WARNING: Error sending end packet
java.net.SocketException: Broken pipe
        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:508)
        at
org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:112)
        at org.apache.jk.core.MsgContext.action(MsgContext.java:293)
        at org.apache.coyote.Response.action(Response.java:182)
        at org.apache.coyote.Response.finish(Response.java:304)
        at
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:204)
        at
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
        at
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:744)
        at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.jav
a:674)
        at
org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocke
t.java:866)
        at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPo
ol.java:684)
        at java.lang.Thread.run(Thread.java:534)
Mar 9, 2006 1:52:12 AM org.apache.jk.common.ChannelSocket
processConnection
WARNING: processCallbacks status 2








---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org





---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: Tomcat just died on our Production Server

Posted by Robert Harper <ro...@iat-cti.com>.
It looks like the socket closed for some reason. You might want to try
catching the exception and doing some clean up so that your app doesn't die.
The connection is lost but you may be able to recover so that you can keep
servicing requests from other connections.

One way to test this would be to use your development server to service the
same requests and while it is busy servicing a request, disconnect the
network and see what happens to you app. The connection will be dead of
course but your app should be coded so that it can recover and not need a
restart so that when the connection is back, your app is ready to service
more requests.

Robert S. Harper
Information Access Technology, Inc.

-----Original Message-----
From: Pete Alvin [mailto:pete@awebabove.com] 
Sent: Thursday, March 09, 2006 10:08 AM
To: users@tomcat.apache.org
Subject: Tomcat just died on our Production Server

Any idea what this means?  At 1:52 our Tomcat just stopped serving 
pages.  Help.. my boss is *pissed* and I have no 
idea how to address this.  I re-started Tomcat and I'm back in 
service... but WHY DID IT HAPPEN?

Thanks in advance.  Pete

Mar 9, 2006 1:52:12 AM org.apache.jk.core.MsgContext action
WARNING: Error sending end packet
java.net.SocketException: Broken pipe
        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:508)
        at 
org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:112)
        at org.apache.jk.core.MsgContext.action(MsgContext.java:293)
        at org.apache.coyote.Response.action(Response.java:182)
        at org.apache.coyote.Response.finish(Response.java:304)
        at 
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:204)
        at 
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
        at 
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:744)
        at 
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.jav
a:674)
        at 
org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocke
t.java:866)
        at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPo
ol.java:684)
        at java.lang.Thread.run(Thread.java:534)
Mar 9, 2006 1:52:12 AM org.apache.jk.common.ChannelSocket 
processConnection
WARNING: processCallbacks status 2








---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org





---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org