Broken Pipe?

[Kristian Rink <kr...@zimmer428.net>]

Folks;

a few days ago, on one of our tomcat servers catalina.out started
filling up with messages like this:

25.07.2007 08:16:43 org.apache.jk.core.MsgContext action
WARNUNG: 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:531) 
 at
org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:121)
[...] org.apache.jk.common.ChannelSocket processConnection 
WARNUNG: processCallbacks status 2

Looking to my own applications log file, I can see which is the servlet
to cause this error (ClientAbortException), but I am not at all sure why
it started showing up all of a sudden. Reading that it's actually a
"Client"AbortException, should I not worry about it and leave things
movin' on as they do? Or is this some more severe issue that needs to
be adressed?

Environment: 
- tomcat 6.0.13 behind an apache2 / mod_jk 1.2.23
- jdk 1.6.0
- Ubuntu Dapper server

TIA and bye,
Kristian

-- 
Kristian Rink * http://zimmer428.net * http://flickr.com/photos/z428/
jab: kawazu@jabber.ccc.de * icq: 48874445 * fon: ++49 176 2447 2771
"One dreaming alone, it will be only a dream; many dreaming together
is the beginning of a new reality." (Hundertwasser)

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