tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kristian Rink <krist...@zimmer428.net>
Subject ClientAbortException / Broken Pipe?!
Date Tue, 14 Aug 2007 13:57:25 GMT

Folks;

still messing around with an error like this: In our system, we offer
customers a service to download files using a servlet. Some weeks ago
(more or less when I considered switching to tomcat 6.0), the following
error frequently started to show up in my log files:

...
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:537) at
org.apache.jk.common.JkInputStream.endMessage(JkInputStream.java:127)
at org.apache.jk.core.MsgContext.action(MsgContext.java:302) at
org.apache.coyote.Response.action(Response.java:183) at
org.apache.coyote.Response.finish(Response.java:305) at
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:205)
at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:283)
at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:773) at
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:703)
at
org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:895)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
at java.lang.Thread.run(Thread.java:619) 14.08.2007 15:38:34
org.apache.jk.common.ChannelSocket processConnection WARNUNG:
processCallbacks status 2
...


whereas I see a "ClientAbortException" caught by my applications
exception handling mechanism. So far, I haven't been able to track this
down, that's why I am kindly asking you for your skilled advice.

What did I do so far trying to get hold of this:

- Tomcat runs on a machine in the LAN, fronted by an apache2 httpd.

- The error does appear both running tomcat 6.0.13 and 5.5.23.

- I initially was using mod_jk 1.2.29 and switched to mod_proxy and
Proxy/ProxyReverse setup just to make sure, and the error appears
no matter whether using mod_jk or mod_proxy.

- Right now, I am using apache2 prefork mpm, played around with
different mpms just to be sure it's not an error related to apache2
itself, but this also didn't really change anything.

- apache2 logging doesn't show any messages whenever such a
"ClientAbortException" is thrown. 

- Customers, however, reported that whenever such a situation happened,
the files downloaded were either 0k sized or corrupted.



And I'm whole-heartedly clueless by now.... :( Is there anything I
forgot to double-check? Using the latest JDK, no tcnative, running
Ubuntu Linux 6.06.1. Applied pretty much every solution attempt I could
come up with using google, including tweaking the HTTP connector setup
in server.xml, removing tcnative, using mod_proxy instead of mod_jk -
no success.  Does anyone around here have any more ideas on how to get
hold of this?

Thanks loads in advance 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


Mime
View raw message