lting?
Regards Per Jonsson
-Original Message-
From: Rainer Jung [mailto:[EMAIL PROTECTED]
Sent: den 23 februari 2007 10:19
To: Tomcat Users List
Subject: Re: Still connection problems between IIS tomcat 5.5.12
OK, my mail was slightly misleading: the other timeouts should *not* bea
a r
... and by the ay: 5.5.12 is pretty outdated ...
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
5w.host=10.182.18.2
worker.ajp15w.port=8009
worker.ajp15w.socket_keepalive=True
worker.ajp15w.socket_timeout=60
---8<---
/Per Jonsson
-Original Message-
From: Rainer Jung [mailto:[EMAIL PROTECTED]
Sent: den 23 februari 2007 09:25
To: Tomcat Users List
Subject: Re: Still connection problems between I
ket_keepalive=True
worker.ajp15w.socket_timeout=60
---8<---
/Per Jonsson
-Original Message-
From: Rainer Jung [mailto:[EMAIL PROTECTED]
Sent: den 23 februari 2007 09:25
To: Tomcat Users List
Subject: Re: Still connection problems between IIS tomcat 5.5.12
Winsock error 10054 is a connecti
Winsock error 10054 is a connection reset.
Do you use socket_timeout in workers.properties? If yes, try without
socket_timeout (but have a look at the other timeout possibilities of
mod_jk). Socket_timeout is difficult to handle at the application=mod_jk
layer.
Any changes on the firewall ar
It's me again, we have not yet solved our problems, but now we have
turned one of the IIS servers to IIS 5 compability mode which made us
get som logs from the tomcat connector.
Short Review of setup:
Tomcat 5.5.12
APR 1.1.0-dev
ispi_redirect.dll 1.2.20
between the iis and tomcat we have a firewa
