Chris- broken pipe means that at one end (more than likely the DB listener you're connecting to somehow dropped) A quick fix is to bump the connectionTimeout up by 5 sec If not bump the mod_proxy.proxytimeout up by 5 secs http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxytimeout
Martin- --------------------------------------------------------------------------- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. --------------------------------------------------------------------------- Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. ----- Original Message ----- From: "c." <[EMAIL PROTECTED]> To: <users@tomcat.apache.org> Sent: Friday, March 23, 2007 12:47 PM Subject: Tomcat mod_proxy_ajp and jk exceptions > Hello, > > I'm using mod_proxy_ajp as my link b/w tomcat and apache. Things are > working well with the exception of getting the following error: > > 2007-03-22 20:02:42,875 [TP-Processor51] WARN > org.apache.jk.core.MsgContext - 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:518) > 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:754) > at org.apache.jk.common.ChannelSocket.processConnection( > ChannelSocket.java:684) > at org.apache.jk.common.ChannelSocket$SocketConnection.runIt( > ChannelSocket.java:876) > at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run( > ThreadPool.java:684) > at java.lang.Thread.run(Thread.java:595) > 2007-03-22 20:02:42,875 [TP-Processor51] WARN > org.apache.jk.common.ChannelSocket - processCallbacks status 2 > > a few times a day. > > This is from a medium traffic e-commerce site (approx. 1000 trans a day) and > it seems to occur when the user is on the secure checkout page and hits the > order button. They complain of being presented with a blank page after > hitting the purchase button. > > Pertinent details from the servlet.xml: > > <Connector address="139.0.0.1" > port="8009" > enableLookups="false" > protocol="AJP/1.3" > minSpareThreads="20" > maxSpareThreads="200" > maxThreads="1024" > connectionTimeout="600000" > /> > > Any ideas as to why this is happening? > > Thanks, > > Chris. >
