Thank you so much for replying.

I actually found the issue and it was simple.  The starter daemon (which I 
don't control, unfortunately) wasn't launching the tomcat installs from the 
proper locations.  It was calling the respongindPROD from the 
initiatingPROD dir every time, no matter which tomcat installation it was 
launching.  Fixing that fixed my issue completely.

Thank you,

Jason T. Countryman

From: Christopher Schultz <>
Sent: Thursday, February 24, 2022 3:55 PM
To: <>
Subject: Re: Configure mulitple installs tomcat 8.5 - 


On 2/23/22 13:50, Jason Countryman wrote:
> Good afternoon,
> On a Centos 7 machine, I have multiple full tomcat installs.
> /var/tomcat_installs/initiatingPROD
> /var/tomcat_installs/respondingPROD
> My app uses a spring configuration for cxf, and uses catalina.base to 
> identify the location for the keystore/truststore, and log4j2 for logging.  
> When I start each individual tomcat using, they report setting 
> CATALINA_HOME and CATALINA_BASE correctly for their respective locations.
>   $ /var/tomcat_installs/initiatingPROD/apache-tomcat-8.5.73/bin/
> /var/tomcat_installs/initiatingPROD/apache-tomcat-8.5.73
> /var/tomcat_installs/initiatingPROD/apache-tomcat-8.5.73
> /var/tomcat_installs/initiatingPROD/apache-tomcat-8.5.73/temp
> Using JRE_HOME:        /usr
> Using CLASSPATH:       
> /var/tomcat_installs/initiatingPROD/apache-tomcat-8.5.73/bin/bootstrap.jar:/var/tomcat_installs/initiatingPROD/apache-tomcat-8.5.73/bin/tomcat-juli.jar
> Tomcat started.
> $ /var/tomcat_installs/respondingPROD/apache-tomcat-8.5.73/bin/
> /var/tomcat_installs/respondingPROD/apache-tomcat-8.5.73
> /var/tomcat_installs/respondingPROD/apache-tomcat-8.5.73
> /var/tomcat_installs/respondingPROD/apache-tomcat-8.5.73/temp
> Using JRE_HOME:        /usr
> Using CLASSPATH:       
> /var/tomcat_installs/respondingPROD/apache-tomcat-8.5.73/bin/bootstrap.jar:/var/tomcat_installs/respondingPROD/apache-tomcat-8.5.73/bin/tomcat-juli.jar
> Tomcat started.
> However, as I follow catalina.out, it appears the values for these are 
> changed somehow, or I have a configuration error causing this (more likely).  
> There is all kinds of crosstalk in the respondingPROD catalina.out showing 
> things from the initiatingPROD installation.  The initiatingPROD 
> catalina.out, however, only has references to what it should.
> I'm setting this up this way so to provide a testing/upgrade path for 
> tomcat/log4j2 updates, and need each of these installations to be agnostic of 
> the other, and really need a way to specify for spring where the keystores 
> are located and they can not be in the classpath.
> There has to be some configuration thing for multiple FULL tomcat 
> installations that I'm missing here causing all this crosstalk for the 
> respondingPROD installation, correct?

All that looks weird. If shows CATALINA_BASE == CATALINA_HOME
and both initiatingPROD and respondingPROD have separate values, then
then nothing should be interfering.

Honestly, if you expect to run them on the same version of Tomcat (oor
eve if you don't!) I would recommend having CATALINA_BASE !=
CATAINA_HOME and have CATALINA_HOME only contain the files that came
from ASF directly. Your CATALINA_BASE will contain your
application-specific stuff.

Anyway, there's no need to complicate things for you like that quite
yet, so ...

What happens if you try this:

1. Stop both Tomcats
2. Delete catalina.out from both installations
3. Start only the initiatingPROD Tomcat process

Look for any log files in EITHER of the two installations. What do you see?


To unsubscribe, e-mail:
For additional commands, e-mail:

This message and any attachments may contain information that is protected by 
law as privileged and confidential, and is transmitted for the sole use of the 
intended recipient(s). If you are not the intended recipient, you are hereby 
notified that any use, dissemination, copying or retention of this e-mail or 
the information contained herein is strictly prohibited. If you received this 
e-mail in error, please immediately notify the sender by e-mail, and 
permanently delete this e-mail.

Reply via email to