You say the page not found errors are good... *IT IS GOOD BECAUSE IT TELLS ME THE SERVER IS BEING HIT. PRIOR TO YOUR HELP THE WRONG SERVER WAS OPENING ON ALL PORTS AND IP's NO LONGER THE CASE. * The configuration of the connectors looks ok
Are there any errors in the logs and have you configured an identifiable error page for both instances? (<error-page> inside web.xml) *THE ERROR LOG IS "BARK" ABOUT: *StandardContext[/balancer]Exception starting filter BalancerFilter java.lang.NoClassDefFoundError: org/apache/commons/digester/Digester* (UNRELATED). THE SERVER (server 2) IS NOT SERVING ANY PAGES, TRIED TO VIEW A GIF THROUGH URL AND IT WOULD NOT LOAD. HONESTLY DO NOT HAVE THE SKILLS TO FIGURE OUT HOW TO GET <ERROR-PAGE> TO WORK RIGHT.* That way you can determine which tomcat is serving the error. Do the other connectors have an address defined *CONNECTORS I ASSUME YOU ARE REFERRING TO ARE PORTS 8009, AND 8109, BOTH HAVE ADDRESSES HARD CODED IN SERVER.XML*. The fact you get a 400 indicates that a tomcat is responding, you now only have to determine if it is the right one and what causes the error (what type of content are you serving, static dynamic) *I AM SITES ARE ALL JSP PAGES (I BELIEVE THAT TEY ARE ALL DYNAMIC) <not a web dev>* On Wed, Oct 29, 2008 at 11:03 AM, Serge Fonville <[EMAIL PROTECTED]>wrote: > You say the page not found errors are good...The configuration of the > connectors looks ok > Are there any errors in the logs and have you configured an identifiable > error page for both instances? (<error-page> inside web.xml) > That way you can determine which tomcat is serving the error. > Do the other connectors have an address defined > The fact you get a 400 indicates that a tomcat is responding, you now only > have to determine if it is the right one and what causes the error (what > type of content are you serving, static dynamic) > > > Regards, > > Serge Fonville > > > On Wed, Oct 29, 2008 at 3:49 PM, dOE <[EMAIL PROTECTED]> wrote: > >> Hi Serge, >> >> Below are the values from both of my server.xml files. I specified the >> address that the port should listen on, and I am unable to open * >> http://192.168.100.2:8080* (GOOD!). When I attempt to open * >> http://192.168.100.2:8180* I get a 400, and *http://192.168.100.1:8180* >> the >> "request" returns "Page Cannot Be Found"(GOOD!). >> >> 192.168.100.1 has ports 8080, 8009 >> 192.168.100.2 has ports 8180, 8109 >> >> The correct ports are open, its just that I can not open the site on >> 192.168.100.2 through Tomcat. >> Should I have only edited one server.xml, rather than hard coding the IP >> in >> both? >> >> (Server 1) 192.168.100.1 >> <!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 --> >> <Connector port="8080" >> maxThreads="150" >> minSpareThreads="25" >> maxSpareThreads="75" >> enableLookups="false" >> redirectPort="8443" >> acceptCount="100" >> debug="0" >> connectionTimeout="20000" >> disableUploadTimeout="true" >> address="192.168.100.1" /> >> >> (Server 2) 192.168.100.2 >> <!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8180 --> >> <Connector port="8180" >> maxThreads="150" >> minSpareThreads="25" >> maxSpareThreads="75" >> enableLookups="false" >> redirectPort="8543" >> acceptCount="100" >> debug="0" >> connectionTimeout="20000" >> disableUploadTimeout="true" >> address="192.168.100.2" /> >> >> >> >> >> >> >> >> >> >> >> On Wed, Oct 29, 2008 at 9:40 AM, Serge Fonville <[EMAIL PROTECTED] >> >wrote: >> >> > Place inside a <Service> element<Connector port="80" protocol="HTTP/1.1" >> > connectionTimeout="20000" >> > redirectPort="443" >> > address="127.0.0.1"/> >> > and the output of netstat contains an entry for 127.0.0.1:80 instead of >> > the usual 0.0.0.0:80 >> > >> > Regards, >> > >> > Serge Fonville >> > >> > On Wed, Oct 29, 2008 at 2:31 PM, dOE <[EMAIL PROTECTED]> wrote: >> > >> >> Serge thanks for the reply... >> >> >> >> so to hard code the IP its just a matter of ONLY adding <Connector >> >> address=' >> >> 192.168.1.1'> ? >> >> >> >> The online document site does not give any syntax examples. >> >> >> >> On Wed, Oct 29, 2008 at 9:17 AM, Serge Fonville < >> [EMAIL PROTECTED] >> >> >wrote: >> >> >> >> > There is an address attribute inside the connector that specifies the >> >> > address of the listening socket >> >> > http://tomcat.apache.org/tomcat-6.0-doc/config/http.html >> >> > http://tomcat.apache.org/tomcat-6.0-doc/config/ajp.html >> >> > >> >> > Hope this helps >> >> > >> >> > Regards, >> >> > >> >> > Serge Fonville >> >> > >> >> > On Wed, Oct 29, 2008 at 2:06 PM, dOE <[EMAIL PROTECTED]> wrote: >> >> > >> >> >> I have a server that I am hosting multiple Tomcat servers from, and >> the >> >> >> issue I am running into is... - I have multiple IP's bound to the >> >> servers >> >> >> interface, Tomcat _1 has port 8080 specified as its connector port. >> >> The >> >> >> second Tomcat_2 has port 8180 set as its conector port in its >> >> server.xml, >> >> >> but regardless of these custom ports I am only able to reach >> Tomcat_1 >> >> >> through 8080, and 8180. Is it possible to hard code the IP you want >> >> that >> >> >> particular instance to listen on? >> >> >> >> >> > >> >> > >> >> >> > >> > >> > >