Well I run in exactly the same environment except it's a RedHat 6.2
(-ish) box

My server.xml is setup like so:
<!-- Define an AJP 1.3 Connector on port 8009 -->
    <Connector className="org.apache.ajp.tomcat4.Ajp13Connector"
               port="8009" minProcessors="3" maxProcessors="15"
               acceptCount="10" debug="0"/>


The connector is setup like so:
# BEGIN workers.properties
worker.list=ajp13
worker.ajp13.port=8009
# change this line to match apache ServerName and Host name in
server.xml
worker.ajp13.host=www.whatever.com
worker.ajp13.type=ajp13
# END workers.properties


HTH.

I can't see anything in your setup which instantly looks wrong but there
appear to be some parameters which are unnessecary, although I'm not
sure. Could it be anything to do with your timeout set to 0?

Apart from that it looks like it could be something on the SQL side
that's causing the problem.

IMHO, have a glance at the sql server logs.

Adam

On Fri, 2004-03-12 at 15:53, Michael GÃrlich (CSC) wrote:
> 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(ChannelSocket.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]

Reply via email to