Interesting. It's actually the other way. telnet to 8008 seemed successful. ---------------------------------------------------------------- $ telnet myhost 8008 Trying 169.193.129.130... Connected to myhost. Escape character is '^]'.
ls HTTP/1.1 400 Bad Request Server: Apache-Coyote/1.1 Transfer-Encoding: chunked Date: Fri, 21 Aug 2009 15:54:14 GMT Connection: close 0 Connection to emimmagg1 myhost closed by foreign host. ---------------------------------------------------------------- But telnet to 8080 was refused: ---------------------------------------------------------------- $ telnet myhost 8080 Trying 1xx.1xx.1xx.1xx... telnet: Unable to connect to remote host: Connection refused --------------------------------------------------------------- This is my browser's response: Unable to connect Firefox can't establish a connection to the server at myhost:8008. * The site could be temporarily unavailable or too busy. Try again in a few moments. * If you are unable to load any pages, check your computer's network connection. * If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web. ~~~~~~~~~~~~~~~~~~~~~~~~ Regards, Sashi ~~~~~~~~~~~~~~~~~~~~~~~~ -----Original Message----- From: André Warnier [mailto:a...@ice-sa.com] Sent: Friday, August 21, 2009 11:39 AM To: Tomcat Users List Subject: Re: Running multiple tomcats Malladi, Sasikanth wrote: > No, no forwarding problems, as I can access the original instance at > http://myhost:8080 > It's just that my instance at http://myhost:8008 is not responding. > It's not the localhost, but a remote Solaris box. > What is the exact error message you are getting in the browser, when you try to access http://myhost:8080 ? And, when you try the following command, do you get an answer, and which one (type exactly as shown, in a command window on your current station) : telnet myhost 8008 (replace "myhost" of course) (and, for comparison, try the same, replacing 8008 by 8080) If you are getting some response that indicates that the server refused the connection on port 8008, then it means that something, between your station and the server, is blocking connections to port 8008 on that server (but letting through connections to port 8080). The server logfiles would not show anything, because the connection is never made. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org