Have you noticed if this affects IE users and Firefox users equally? I ask because there's a known issue (that I've never seen an actual answer to) where IE causes these exceptions frequently with no ill effect to anything (other than the overhead of handling the exception in the VM on the server). I'd bet a box of donuts that it only happens for IE users.
-- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com AIM/Yahoo: fzammetti MSN: [EMAIL PROTECTED] Author of "Practical Ajax Projects With Java Technology" (2006, Apress, ISBN 1-59059-695-1) and "JavaScript, DOM Scripting and Ajax Projects" (2007, Apress, ISBN 1-59059-816-4) Java Web Parts - http://javawebparts.sourceforge.net Supplying the wheel, so you don't have to reinvent it! On Tue, August 14, 2007 9:57 am, Kristian Rink wrote: > > 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: [EMAIL PROTECTED] * 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
