-----Original Message-----
From: Kiran Badi [mailto:[email protected]]
Sent: Tuesday, 12 May, 2015 10:54 AM
To: Tomcat Users List
Subject: Re: Tomcat 7.0.57 - Deployment Issue
for some reasons it's not going well. Its getting deployed as single app
www.mywebapp1.com\mywebapp2\ rather than 2 seperate sites.
mywebapp1 is deployed as root.war
and I uploaded the webapp2.war in webapps folder and edited server.xml with
below details,
<Host name="www.webapps2.com" appBase="/home/myhostid/tomcat/webapps">
<Alias>www.webapps2.com</Alias>
<Alias>myhostid.myhost.myhostserver.com</Alias>
<Context path="/manager" debug="0" privileged="true"
docBase="/home/myhostid/tomcat/webapps/webapps2">
<Valve className="org.apache.catalina.valves.AccessLogValve"
directory="logs"
prefix="webapps2_access_log." suffix=".txt"
pattern="%h %l %u %t "%r" %s %b" />
</Context>
</Host>
I did not touch webapp1 app since its deployed as root.war and its working
fine..
One more thing, do need have one more connector tag as I see these error on
catalina logs
May 11, 2015 7:11:51 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-17701"] May 11, 2015 7:11:51 PM
org.apache.coyote.AbstractProtocol init
SEVERE: Failed to initialize end point associated with ProtocolHandler
["http-bio-17701"]
java.net.BindException: Address already in use <null>:17701
---------------------
Below is my reply
Hi
It maybe because of the existing default configuration, that is folder
%TOMCAT_HOME%/webapp may be the default config for www.webapps1.com.
And if you are deploying mywebapp2 under the folder %TOMCAT_HOME%/webapp/ like
%TOMCAT_HOME%/webapp/mywebapp2
it will be accessible from www.mywebapp1.com context
I suggest you rewrite the server.xml by hand from scratch with one vhost config
for each domain and different root context.
*it help you get better solution if you actually post the server.xml with
unnecessary contents stripped out
With regards
Prabhu
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]