. The result will be that
Tomcat will simply send the thread back to it's pool to wait for another
connection.
If you upgrade your Tomcat version, that message will be logged at DEBUG
level (and so shouldn't show up with a production configuration).
>
> Jan 8, 2009 1:40:10 P
ext 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)
.
=
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
I am seeing a lot of warning messages in catalina.out
with the stack trace show below.
We are using tomcat 5.5.16 with apache 2 and ajp13 to
connect. Can someone shed some light on this?
Thanks.
=
WARNING: Error sending end packet
java.net.SocketException: Broken
Hello,
Just built a new box.
it is Centos 5
Apache/2.2.3
tomcat-5.5.15
mod_jk-1.2.23-apache-2.2.x-linux-x86_64.so
i am getting tons of these in my log file:
I would appreciate any help in debugging this
thanks
Jan 10, 2008 6:19:50 AM org.apache.jk.core.MsgContext action
WARNING: Error sending
Thank you again for any help!!
Jul 27, 2006 11:44:48 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