tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mladen Turk <>
Subject Re: Sharing the same $CATALINA_BASE
Date Tue, 17 Nov 2009 09:54:20 GMT
On 17/11/09 10:40, Rainer Jung wrote:
> On 17.11.2009 07:51, Mladen Turk wrote:
>> Hi,
>> Anyone knows what might be the pitfalls of sharing the
>> CATALINA_BASE among multiple TC instances?
>> Presume you have a way to bind multiple instance's
>> Connectors to the same ports what might be other problems?
>> For example app management (stop/start) is not recognized
>> across instances, although deployment is, thanks to
>> the file system scanning. Adding some shared status resource
>> would handle the first one thought.
>> Logging looks good, although at least DEBUG would need
>> to carry an instance pid.
>> Anything else?
> temp: Depends on what the app does with it
> work: Update JSP and multiple Japsers generating servlet code to the
> same file ...
> webapps: inconsistencies possible when doing deploy/undeploy (details
> unclear)
> logs: catalina.out behaviour might be platform dependent (multiple
> processes writing to the same file)
>        juli-Logs: no idea, whether the implementation or the JVM classes
> append each line, or lines might get corrupted
>        log4j: possibly the same as juli

Thanks for the places to look at.

> Never tried it. Is it worth the experiment? If you only want to share
> the config, I would prefer to separate at least temp, logs and work per
> instance.

Nope it's for embedding tomcat instance directly inside
web server worker (Httpd/IIS)


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

View raw message