RE: Multiple Tomcat Instances with Multiple IPs
I've been out for a few days; but, thanks for your input. It does seem like a firewall issue; and I've put a ticket into the right people to open up that port. When it's completed, I'll continue and see what I get. Again, thanks for your input. ___ Regards, From: chuck.caldar...@unisys.com To: users@tomcat.apache.org Date: Fri, 19 Aug 2011 15:54:47 -0500 Subject: RE: Multiple Tomcat Instances with Multiple IPs From: Vickie Troy-McKoy [mailto:vtmc...@hotmail.com] Subject: RE: Multiple Tomcat Instances with Multiple IPs When I put in the DNS name or the IP address of the newly defined interface with the correct port in the browser, I get page can not be displayed. Use netstat -ap to make sure Tomcat is listening on the IP:port you think it should be. If it is, then you might have a firewall blocking that port. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Multiple Tomcat Instances with Multiple IPs
From: Vickie Troy-McKoy [mailto:vtmc...@hotmail.com] Subject: Multiple Tomcat Instances with Multiple IPs Instead of running it on different ports, we decided to run it on a different IP address. Each Tomcat must still have a unique shutdown port configured in its Server element. In server.xml, I added the address=xxx.xx.x.xx parameter for all the ports. That's not correct; the address attribute can only be used on Connector elements, not the Server element. Also, it it had better be address=xxx.xx.x.xx, not address=xxx.xx.x.xx. I played with the Host name parameter-putting in the fqn DNS name and tried the IP address there. Incorrect and unnecessary - put it back the way it was. I tried adding address=xxx.xx.x.xx for the Server shutdown port. See above; there is no address attribute for Server (it's listening only on 127.0.0.1 for the shutdown command). WARNING: Unknown default host [localhost] for connector [Connector[HTTP/1.1-8080]] WARNING: Unknown default host [localhost] for connector [Connector[AJP/1.3-8009]] That's because you broke your Host configuration; again, put it back the way it was. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Multiple Tomcat Instances with Multiple IPs
Thanks for your input; however, the very 1st time I ONLY changed ALL of the Connector ports to add address=xxx.xx.x.xx. However, when I tried to access the url, the page could not be displayed. I tried accessing it by the IP and the fqn. Only then, did I start playing with the Host name and the Server elements. I am running Tomcat 7.0.14 I did see one inconsistency; /etc/hosts has the new IP address, but it has a typo for the fqn. When I did an nslookup, the IP address is there but the name is one letter off. Since I am not the Unix sys admin, I do not have access to correct that small change and have put in a ticket to have that done--separation of duties. Could that possibly be the reason why I am getting the page could not be displayed--even though I'm trying to access it by the IP address--when the fqn did not work. Also for the shutdown port, should I use a different port #--since I have 2 tomcat instances installed and it only listens on the 127.0.0.1.? Thank you, ___ Regards, From: chuck.caldar...@unisys.com To: users@tomcat.apache.org Date: Fri, 19 Aug 2011 14:43:33 -0500 Subject: RE: Multiple Tomcat Instances with Multiple IPs From: Vickie Troy-McKoy [mailto:vtmc...@hotmail.com] Subject: Multiple Tomcat Instances with Multiple IPs Instead of running it on different ports, we decided to run it on a different IP address. Each Tomcat must still have a unique shutdown port configured in its Server element. In server.xml, I added the address=xxx.xx.x.xx parameter for all the ports. That's not correct; the address attribute can only be used on Connector elements, not the Server element. Also, it it had better be address=xxx.xx.x.xx, not address=xxx.xx.x.xx. I played with the Host name parameter-putting in the fqn DNS name and tried the IP address there. Incorrect and unnecessary - put it back the way it was. I tried adding address=xxx.xx.x.xx for the Server shutdown port. See above; there is no address attribute for Server (it's listening only on 127.0.0.1 for the shutdown command). WARNING: Unknown default host [localhost] for connector [Connector[HTTP/1.1-8080]] WARNING: Unknown default host [localhost] for connector [Connector[AJP/1.3-8009]] That's because you broke your Host configuration; again, put it back the way it was. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Multiple Tomcat Instances with Multiple IPs
From: Vickie Troy-McKoy [mailto:vtmc...@hotmail.com] Subject: RE: Multiple Tomcat Instances with Multiple IPs the very 1st time I ONLY changed ALL of the Connector ports to add address=xxx.xx.x.xx. Since you didn't change the shutdown port on the second Tomcat instance, it would not have started properly; you should be able to see that in the logs. Also, since you have configured Tomcat to use a specific IP address, you must use that IP address (or its DNS equivalent) from any client you want to access that Tomcat - even if the client is on the same machine as Tomcat. /etc/hosts has the new IP address, but it has a typo for the fqn. That shouldn't matter, unless your client is running on the machine with the incorrect /etc/hosts *and* you use the what the DNS name should be. Tomcat itself doesn't care what's in /etc/hosts, only DNS lookup does. Also for the shutdown port, should I use a different port # --since I have 2 tomcat instances installed and it only listens on the 127.0.0.1.? Not should, must. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Multiple Tomcat Instances with Multiple IPs
It definitely started up clean; and I see why. The existing instance is using port 9005 on the shutdown connector. So, everything is coming up clean--no errors in the logs. The only change I made was adding the address element to the Connectors. I am using port 8005 in the 2nd instance because the 1st instance is using 9005. When I put in the DNS name or the IP address of the newly defined interface with the correct port in the browser, I get page can not be displayed. ___ Regards, From: chuck.caldar...@unisys.com To: users@tomcat.apache.org Date: Fri, 19 Aug 2011 15:22:44 -0500 Subject: RE: Multiple Tomcat Instances with Multiple IPs From: Vickie Troy-McKoy [mailto:vtmc...@hotmail.com] Subject: RE: Multiple Tomcat Instances with Multiple IPs the very 1st time I ONLY changed ALL of the Connector ports to add address=xxx.xx.x.xx. Since you didn't change the shutdown port on the second Tomcat instance, it would not have started properly; you should be able to see that in the logs. Also, since you have configured Tomcat to use a specific IP address, you must use that IP address (or its DNS equivalent) from any client you want to access that Tomcat - even if the client is on the same machine as Tomcat. /etc/hosts has the new IP address, but it has a typo for the fqn. That shouldn't matter, unless your client is running on the machine with the incorrect /etc/hosts *and* you use the what the DNS name should be. Tomcat itself doesn't care what's in /etc/hosts, only DNS lookup does. Also for the shutdown port, should I use a different port # --since I have 2 tomcat instances installed and it only listens on the 127.0.0.1.? Not should, must. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Multiple Tomcat Instances with Multiple IPs
From: Vickie Troy-McKoy [mailto:vtmc...@hotmail.com] Subject: RE: Multiple Tomcat Instances with Multiple IPs When I put in the DNS name or the IP address of the newly defined interface with the correct port in the browser, I get page can not be displayed. Use netstat -ap to make sure Tomcat is listening on the IP:port you think it should be. If it is, then you might have a firewall blocking that port. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
