I don't deny the stacktraces the original poster included are from a connector.
But... the original problem relates to loosing a 'database connection pool', which should have nothing at all to do with the jk connector. I don't think it's very clear yet, what is *actually* going on. If you are correct, and the database thing is a red herring, then fine, he can ignore that annoying (and common) jk message. I get them all the time, I've asked a couple times for help in getting them shut off... oh well. That's jk for you. If, otoh, he's got a database problem, and while trying to diagnose the trouble, noticed those common jk errors, and related the two (his database trouble to the jk error messages), then his trouble is *not* with jk, but with his connection pool. He did, after all, say "I think...". I was attempting to eliminate a very common cause of 'lost connections' to a mysql database. > This is a Coyote connector exception -- which is the HTTP/1.1 protocol > connector. It allows you to connect directly to Tomcat using a browser, > instead of going through Apache. And.. who first mentioned the Coyote HTTP connector ?? I see in the original poster's server.xml: protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler" that looks the configuration for an AJP 1.3 connection to Apache. > -----Original Message----- > From: Christopher Schultz [mailto:[EMAIL PROTECTED] > Sent: Friday, March 12, 2004 11:17 AM > To: Tomcat Users List > Subject: Re: problem with mod_jk 1.2: error in action code > > > All, > > > when you specify the connection to mysql, are you including the > > 'autoreconnect=true' parameter? If not, the connections > will be closed > > by mysql after (I think) 8 hrs. > > I'm not sure why everyne's caught up in database connection > code. This > is a Coyote connector exception -- which is the HTTP/1.1 protocol > connector. It allows you to connect directly to Tomcat using > a browser, > instead of going through Apache. > > Usually the "Broken Pipe" means the the client hung up before > listening > for all the data. That could mean pressing the STOP button on the > browser, following another link before the page fully loads, > or pressing > the back button. > > I wouldn't worry too much about it, unless your users are > somehow being > affected. > > -chris > > > > > > >>-----Original Message----- > >>From: Michael G�rlich (CSC) [mailto:[EMAIL PROTECTED] > >>Sent: Friday, March 12, 2004 9:53 AM > >>To: Tomcat Mailinglist > >>Subject: problem with mod_jk 1.2: error in action code > >> > >> > >>Hello, > >> > >>I've got problems with a tomcat web application, that > >>establishes a connection pool to a database (mysql). This > >>connection pool is lost after an unspecified period of time > >>the system wasn't used (f.e. 8 houres). > >> > >>I think the problem is due to the mod_jk connector between > >>apache and tomcat. > >> > >>The web application is accessible over apache 1.3.27, that > >>connects to tomcat 4.1.27 via jk connector mod_jk 1.2.25. > >> > >>The exception I got in catalina.out is: > >> > >>10.03.2004 15:59:58 org.apache.jk.server.JkCoyoteHandler action > >>SCHWERWIEGEND: Error in action code > >>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:407) > >>at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:599) > >>at > >>org.apache.jk.server.JkCoyoteHandler.action(JkCoyoteHandler. > java:385) > >>at org.apache.coyote.Response.action(Response.java:222) > >>at org.apache.coyote.Response.finish(Response.java:343) > >>at > >>org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler. > java:268) > >>at > org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) > >>at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:604) > >>at > >>org.apache.jk.common.ChannelSocket.processConnection(ChannelSo > >>cket.java:562) > >>at > org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:679) > >>at > >>org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run( > >>ThreadPool.jav > >>a:619) > >>at java.lang.Thread.run(Thread.java:534) > >>10.03.2004 15:59:58 org.apache.jk.common.ChannelSocket > >>processConnection > >>INFO: server has been restarted or reset this connection > >> > >>The HTTP connector defined in tomcats server.xml is: > >> > >><Connector className="org.apache.coyote.tomcat4.CoyoteConnector" > >>port="8009" minProcessors="5" maxProcessors="75" > >>enableLookups="false" redirectPort="8443" acceptCount="10" > >>debug="5" connectionTimeout="0" useURIValidationHack="false" > >>protocolHandlerClassName="org.apache.jk.server.JkCoyoteHandler" > >>scheme="http" > >>secure="false" /> > >> > >>The log in mod_jk.log shows the following: > >> > >>[Wed Mar 10 15:59:58 2004] [jk_ajp_common.c (1052)]: ERROR > >>sending data to client. Connection aborted or network > >>problems [Wed Mar 10 15:59:58 2004] [jk_ajp_common.c (1303)]: > >>ERROR: Client connection aborted or network problems > >> > >>Here is the summary of my environment options: > >>- tomcat 4.1.27 > >>- apache 1.3.27 > >>- mod_jk 1.2.25 > >>- Suse Linux 7.2 > >>- Java 2 RE Standard Edition, Version 1.4.1 (build > Blackdown-1.4.1-01) > >> > >>My special problem is, that I'm not able to reproduce the > >>error, it occurs after an unspecified period of time. I found > >>nothing related to this problem. Any ideas? > >> > >>Thanks in advance > >>M.Goerlich > >> > >> > >>------------------------------------------------------------ > --------- > >>To unsubscribe, e-mail: [EMAIL PROTECTED] > >>For additional commands, e-mail: [EMAIL PROTECTED] > >> > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
