Error 54 translates to 10054 winsock error, which is "connection reset by peer".
No, opening the port for TCP is enough. It looks like you might be connecting to something else. You should sniff on your tomcat server to check, if the request really reaches the tomcat machine. Regards, Rainer Swaroop George schrieb: > I have a machine sitting in the DMZ with IIS 6.0 as the web server. I > am trying to redirect request to an internal server running Tomcat > sitting behind the firewall using isapi_redirect.dll > > I have opened up port 8009 which is defined as the AJP1.3 connector in > the server.xml. 8009 has been opened up in the firewall for TCP > communication. > But the reverse proxy redirection fails with the following message > > [Thu May 03 20:43:42 2007] [error] jk_ajp_common.c (961): Can't > receive the response message from tomcat, network problems or tomcat > is down (10.170.4.96:8009), err=-54 > [Thu May 03 20:43:42 2007] [error] jk_ajp_common.c (1503): Tomcat is > down or refused connection. No response has been sent to the client > (yet) > [Thu May 03 20:43:42 2007] [info] jk_ajp_common.c (1721): Receiving > from tomcat failed, recoverable operation attempt=0 > [Thu May 03 20:43:42 2007] [info] jk_ajp_common.c (1749): Sending > request to tomcat failed, recoverable operation attempt=1 > > Should I be openeing up the port for a different kind of traffic other > than TCP --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
