Try changing your <Engine> names to match your <Service> names. It will create separate directories underneath <tomcat-home>/conf/
<Service name="RequestsFromPort6000">
<Connector protocol="HTTP/1.1" port="6000"/>
<Engine debug="0" defaultHost="localhost" name="RequestsFromPort6000">
<Host appBase="c:\projects" name="localhost"
unpackWARs="false" autoDeploy="false" deployOnStartup="false">
<Context docBase="app6000" path="/app6000" reloadable="false"/>
</Host>
</Engine>
</Service>
<Service name="RequestsFromPort7000">
<Connector protocol="HTTP/1.1" port="7000"/>
<Engine debug="0" defaultHost="localhost" name="RequestsFromPort7000">
<Host appBase="c:\projects" name="localhost"
unpackWARs="false" autoDeploy="false" deployOnStartup="false">
<Context docBase="app7000" path="/app7000" reloadable="false"/>
</Host>
</Engine>
</Service>Each <Engine> gets its own directory for storing the app7000.xml files. You should see this:
<tomcat-home>/conf/RequestsFromPort6000/localhost/app6000.xml <tomcat-home>/conf/RequestsFromPort7000/localhost/app7000.xml
But you might be right. Because they are both called "localhost" your requests might get mixed up. Give it one last try though before you have to have two instances of Tomcat running.
Charlie
Gary Hirschhorn said the following on 4/21/2005 12:53 PM:
Thanks for the response. However, it still didn't work.
I assume the changes you made were to remove the leading "/" from the docBase. I am guessing the problem is that my Host elements have the same name, and the second one is overriding the first. Unfortunately, it looks like the Host elements need to have the same name as I think the name must represent a name that the local DNS recognizes.
At this point, we are just going to live with a single Service that uses both ports. The reason for trying this in the first place was that we wanted to use our firewall to allow one port to be accessible from the outside that would see our "public" applications, while the second port would be accessible only within our company. This port would allow access to some internal applications. We are using Tomcat security to password-protect the access anyway, but we were hoping have the additional security of not allowing any traffic from the outside at all. (By the way, I think we could accomplish what we want with 2 Tomcat installations, but there are other reasons why that is not desirable.)
-----Original Message-----
From: Raghupathy,Gurumoorthy
[mailto:[EMAIL PROTECTED] Sent: Wednesday, April 20, 2005 2:12 AM
To: 'Tomcat Users List'
Subject: RE: Multiple services in single Tomcat instance
Try this
<Service name="RequestsFromPort6000">
<Connector protocol="HTTP/1.1" port="6000"/>
<Engine debug="0" defaultHost="localhost" name="Standalone">
<Host appBase="c:\projects" name="localhost" unpackWARs="false"
autoDeploy="false" deployOnStartup="false">
<Context docBase="app6000" path="/app6000"
reloadable="false"/>
</Host>
</Engine>
</Service>
<Service name="RequestsFromPort7000"> <Connector protocol="HTTP/1.1" port="7000"/> <Engine debug="0" defaultHost="localhost" name="Standalone"> <Host appBase="c:\projects" name="localhost" unpackWARs="false" autoDeploy="false" deployOnStartup="false"> <Context docBase="app7000" path="/app7000" reloadable="false"/> </Host> </Engine> </Service>
-----Original Message-----
From: Gary Hirschhorn [mailto:[EMAIL PROTECTED] Sent: 19 April 2005 16:58
To: Tomcat Users List
Subject: RE: Multiple services in single Tomcat instance
We are using all of the following URL formats to access Tomcat. There is a singe IP address on the machine, and a single domain name registered for the IP address.
http://localhost:6000/app6000
http://localhost:7000/app7000
http://machinename.hostname.com:6000/app6000 http://machinename.hostname.com:7000/app7000
-----Original Message-----
From: Raghupathy,Gurumoorthy
[mailto:[EMAIL PROTECTED] Sent: Tuesday, April 19, 2005 7:56 AM
To: 'Tomcat Users List'
Subject: RE: Multiple services in single Tomcat instance
How are you accessing tomcat ?
http://localhost:7000/ http://localhost:6000/
???
-----Original Message-----
From: Gary Hirschhorn [mailto:[EMAIL PROTECTED] Sent: 19 April 2005 15:34
To: tomcat-user@jakarta.apache.org
Subject: Multiple services in single Tomcat instance
We would like to have a single Tomcat instance running as a web server that allows requests received on one port to go to one context and requests on another port to go to a second context. Is there a way to do this? We tried putting the following in our server.xml, but requests meant for the first service (port 6000) were recieved by the second service (port 7000). Thank you for any help.
<Service name="RequestsFromPort6000">
<Connector protocol="HTTP/1.1" port="6000"/>
<Engine debug="0" defaultHost="localhost" name="Standalone">
<Host appBase="c:/projects" name="localhost" unpackWARs="false"
autoDeploy="false" deployOnStartup="false">
<Context docBase="/app6000" path="/app6000"
reloadable="false"/>
</Host>
</Engine>
</Service>
<Service name="RequestsFromPort7000"> <Connector protocol="HTTP/1.1" port="7000"/> <Engine debug="0" defaultHost="localhost" name="Standalone"> <Host appBase="c:/projects" name="localhost" unpackWARs="false" autoDeploy="false" deployOnStartup="false"> <Context docBase="/app7000" path="/app7000" reloadable="false"/> </Host> </Engine> </Service>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
