awarnier wrote:
>
> Just to try to eliminate the obvious :
> - is Tomcat really listening on port 8009 ?
> "netstat -an" will tell you.
> - is port 8009 not being blocked by the Windows firewall or such ?
> you can slso try "telnet localhost 8009" (if it works, Tomcat will
> accept and then close the connection; the error should be different if
> you cannot even reach the 8009 port though)
>
Thanks for the reply, and yes indeed, I've run out of my knowledge of what
to eliminate. I'd checked the netstat already and there was a Tomcat6.exe
process running on 8009. I've now done a successful telnet as well (though
Tomcat doesn't close the connection).
Netstat shows Tomcat6.exe listening on 8009 8080 8005 2037 2040 2041 2042
2043. I suppose the only question mark I have there is that there is no 8443
as the Servlet.xml defines the http connector and the ajp connector as
having a redirectPort 8443. But I assume that is just to do with ssl, as it
works fine when I go straight to 8080.
<Connector port="8080" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8443" />
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" />
--
View this message in context:
http://old.nabble.com/IIS-redirect-stops-at--xxx--is-a-servlet-url---should-redirect-to-ajp13-tp26495411p26496799.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
