Hi, I think I just managed to stop the applications from multiplying. I added parameter reloadable="false" to the Context elements of both Services. However now Tomcat is saying that the other service's servlet "is not available", as if its web.xml was misconfigured...
On 2/22/06, Chun Wei Ho <[EMAIL PROTECTED]> wrote: > > I am facing a very similar problem here. I use Quartz/Spring to jump > start some background processing threads within Tomcat, and I get two > threads [Quartz_Scheduler_Worker_?] running the same class in the > background (when there should only be one thread). > > It should be somewhat related to Engine/Host config, because I've > configured the two Hosts but only one has the database connectors, and > in my logs one thread runs fine to completion, while the other fails > to find the database, and spams horribly. > > Can anyone let me know where my error is, or what I am doing wrong in > my configuration? The link to the discussion for his solution doesn't > seem to suit my configuration. > > I run two hosts: www.server.com/ runs application > /opt/tomcat5/webapps/ROOT.war > and specialapp.server.com/ runs application > /opt/tomcat5/webapps2/specialapp.war > > Below server.xml snippet: > <Engine name="Catalina" defaultHost="localhost"> > <Host name="specialapp.server.com" appBase="/opt/tomcat5/webapps2" > unpackWARs="true" autoDeploy="true" > xmlValidation="false" xmlNamespaceAware="false"> > <Context path="" docBase="specialapp" debug="0" > reloadable="true"/> > <Logger className="org.apache.catalina.logger.FileLogger" > prefix="specialapp." suffix=".txt" timestamp="true"/> > </Host> > > <Host name="server.com" appBase="/opt/tomcat5/webapps" > unpackWARs="true" autoDeploy="true" > xmlValidation="false" xmlNamespaceAware="false"> > <Alias>www.hyperspace.com</Alias> > <Context path="" docBase="ROOT" debug="0" reloadable="true"/> > <Logger className="org.apache.catalina.logger.FileLogger" > prefix="server." suffix=".txt" timestamp="true"/> > </Host> > </Engine> > </Service> > </Server> > > > > > ----- Original Message ----- > > From: "Antti Ollilainen" <[EMAIL PROTECTED]> > > To: "Tomcat Users List" <users@tomcat.apache.org> > > Sent: Wednesday, February 22, 2006 2:23 PM > > Subject: Re: Multiple services in single Tomcat instance > > > > > > Hi, > > > > Here is a link to the archived discussion which helped me to configure > the > > services up and running: > > http://marc.theaimsgroup.com/?l=tomcat-user&m=111411822627845&w=2 > > > > On 2/21/06, Biernesser, Beth <[EMAIL PROTECTED]> wrote: > > > > > > I am also interested in this issue ... I am setting up the same > > > situation. If anyone has information, could they also include me in > the > > > reply? Thanks so much! > > > > > > -----Original Message----- > > > From: Antti Ollilainen [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, February 21, 2006 10:24 AM > > > To: users@tomcat.apache.org > > > Subject: Multiple services in single Tomcat instance > > > > > > Hello, > > > > > > I'm configuring a single Tomcat instance to serve two separate web > > > applications. The applications are on separate ports and one is > accessed > > > over HTTP while the other one over HTTPS. I managed to get the webapps > > > configured so that each is its own Service in the server.xml. Actually > > > there was a discussion about this in last April with the same subject > > > and I got the tip to use the same name for Engine and Host inside the > > > Service. > > > > > > However, I have another problem now: When I start the server, both web > > > applications seem to start twice. It seems that all application > threads > > > which are initially started are duplicated because both applications > log > > > twice their startup info. I'm using log4j for logging and it seems > that > > > the log lines are not simply duplicated but they originate from > separate > > > threads. > > > > > > Has anyone experience from this kind of configuration or encountered > the > > > same problem? > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > Apa. > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Apa.