We already have that: worker.ajp15w.type=ajp13 worker.ajp15w.host=xx.xx.xx.xx worker.ajp15w.port=8009 worker.ajp15w.socket_keepalive=True worker.ajp15w.socket_timeout=60
I guess that you are talking about what we have specified as "worker.ajp15w.socket_keepalive=True" Right? Or is there an undocumented "worker.xxx.keepalive" ? /Peter 2006/10/17, Mladen Turk <[EMAIL PROTECTED]>:
Peter Olin wrote: > This is what I found in the Tomcat log, and I guess that this is the last > thing that happened before the IIS-Tomcat connection stopped working. > > 2006-10-16 23:20:29 [EMAIL PROTECTED]: > Exception Processing ErrorPage[errorCode=404, location=/index.jsp] > ClientAbortException: java.net.SocketException: Software caused connection > abort: socket write error > at org.apache.coyote.tomcat5.OutputBuffer.realWriteBytes( OutputBuffer.java > :373) Right, this means that you have a s**t of the firewall that does not send the FIN packets when it cuts the inactive connections, or it only cuts one end of the socket. You might try setting the worker.xxx.keepalive=On for each AJP worker. It will send the keepalive packet on opened socket and can detect those firewall cases that behave like cable unplugging. Regards, Mladen. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Peter Olin
