I do it by assigning to each server a unique port number, no? If I am correct, what do I need to do to make the 2nd port number ping-able and web-accessible?
We have been running Apache; we want to install a second web-server independently on the same box: Tomcat. Apache runs fine on port 80. We configured Tomcat with 8080 in the config file (server.xml I think). Tomcat does not run correctly with 8080. However, in a test performed while the Apache was shut down, Tomcat ran fine using 80. Nor, for that matter, does our Apache run on 8080. Therefore Port 8080 seems to be the problem.
If I am correct that different web servers are differentiated by unique port numbers on the same box, what do I need to do to enable port 8080 (or any other port for that matter)?
(1) add an entry to the DNS?
(2) assign rights enabling the port to be accessible through the firewall?
2. We then ported the Tomcat to our development server, which lies behind a firewall from my machine. Attempts from my machine to hit our dev server url, http://220.127.116.11:8080, failed. Similar attempts to hit the Tomcat on dev server port 80 (after Apache which normally runs on port 80 had been shut down) succeeded.
You should talk to the folks who set up the firewall(s).
Try the 'traceroute' utility to see what is happening with differnt ports (utility named differently depending on your OS).
I think you have a wall dropping packets on the floor (i.e. port is blocked).
Joined: Apr 08, 2003
Thank you all for your help on this. My solution--at least for the time being--was a workaround: I setup the Apache as a proxy server, which would forward calls to my application on Tomcat. It seems like pretty standard web configuration technique, but I had never set it up before.
I thought I might include the information in case anyone might find it useful.
To set up this kind of Apache/Tomcat configuration, I consulted the following link:
one caveat: if you are using Apache 2.0 you need only add a LoadModule instruction for the proxy module. You MUST not insert an additional AddModule line. The docs say that for Apache 2.0 you MAY omit the AddModule instruction, but I found that you MUST omit it, or the configuraiton won't work.