On top of the previous error in the log tomcat log file, the following error
shows up in the httpd error log:

[Thu Mar 22 19:55:23 2007] [error] (70007)The timeout specified has expired:
ajp_ilink_receive() can't receive header
[Thu Mar 22 19:55:23 2007] [error] ajp_read_header: ajp_ilink_receive failed
[Thu Mar 22 19:55:23 2007] [error] (120006)APR does not understand this
error code: proxy: read response failed from 139.0.0.1:8009 (139.0.0.1)

On 3/23/07, c. <[EMAIL PROTECTED]> wrote:

Looking at the server.xml connectionTimeout, I've set the value to 600000,
600 seconds not 60 seconds, could I be holding onto the connection for too
long?  The reason I'm asking is 'cause I don't think adding another five
seconds to the 600 will make a difference, adding five seconds to 60 could
be relevant.

chris.

On 3/23/07, c. <[EMAIL PROTECTED]> wrote:
>
> I'll try upping the connection timeouts, but aside from the problem of
> dropped connections what I'm really confused about is why there is a jk
> exception (org.apache.jk.common.ChannelSo
> >
> > cket.send(ChannelSocket.java:518)) when I'm using mod_proxy_ajp, NOT
> > mod_jk.
>
>
>
> Chris.
>
>
>
> On 3/23/07, Christopher Schultz <[EMAIL PROTECTED]> wrote:
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Martin,
> >
> > Martin Gainty wrote:
> > > broken pipe means that at one end (more than likely the DB listener
> > you're connecting to somehow dropped)
> >
> > Unlikely:
> >
> > >> 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)
> >
> > Looks like the JK connector to me, not some database connection.
> >
> > > 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
> >
> > Note that the OP was asking about mod_jk, and you are suggesting a fix
> > for mod_proxy_ajp :(
> >
> > - -chris
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.7 (MingW32)
> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> >
> > iD8DBQFGBA2W9CaO5/Lv0PARApNPAKCMQVsbqgUN0cr7Ln3hLBv2jkriPgCggr3e
> > i7V9vlv9xaAWtA1bl7PH3fo=
> > =7dhr
> > -----END PGP SIGNATURE-----
> >
> > ---------------------------------------------------------------------
> > To start a new topic, e-mail: users@tomcat.apache.org
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>

Reply via email to