tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Laurie Miller-Cook <>
Subject RE: Changing Sever.xml without restarting Tomcat 8.5
Date Tue, 24 Jul 2018 09:54:58 GMT
Hi Chris

You mentioned the below in your reply

"You might also want to consider having separate Tomcat instances per domain. That might be
more manageable, though it will require more memory on your server(s)."

Is there a best practice guide to what we are trying to achieve, multiple domains on one server,
we are new to Tomcat, so we are implementing what we can find in documentation on the web?

We need to be able to supply each customer the same IP Port, say 80 or 443, if we have multiple
instances of Tomcat on one server then would we need a proxy in front (for wants of better
words) which could then direct the customers to the correct websites and hence get the same
IP Port.  We also use SSL so I assume wildcard certificate would need to be applied to each
Tomcat instance?

Would each instance of Tomcat require its own JVM, hence your comment about more memory on
the servers, do you know of any resourcing guide lines for multiple instances on Tomcat on
one server?

Sorry for all the questions.

All the best

Laurie Miller-Cook
dd: +44 (0)1252 607220

-----Original Message-----
From: Christopher Schultz <> 
Sent: Monday, July 23, 2018 7:33 PM
Subject: Re: Changing Sever.xml without restarting Tomcat 8.5

Hash: SHA256


On 7/23/18 12:25 PM, Laurie Miller-Cook wrote:
> Hi there,
> I have an issue where we have multiple virtual hosts in separate base 
> directory's on a single Tomcat installation.  If I need to change 
> something within server.xml I need to restart Tomcat which means I 
> need to do this within an outage window as it affects all of the 
> Websites, is there a way of reloading the server.xml without  
> restarting Tomcat?
> As a bit of background we have a wildcard domain, so 
> <clientname>.<Domain>.com so we have created multiple webapp 
> directories with their own Manage and have multiple entries in the  
> server.xml file for the different hosts.
> What need to be able to do is, for example, is add another host to  
> the xml site and get that to take effect automatically without the  
> need to restarting Tomcat as this restarts all the other websites and 
> hence gives outages to our customers.
> Any help would be greatly appreciated.

Tomcat won't reload server.xml. It's just too complicated to determine what has changed and
how to perform an in-place reinit that only does what is "necessary".

On the other hand, JMX is very powerful and you can make runtime changes to Tomcat using that.
Maybe you can consider performing two operations whenever you need to add a virtual host:

1. Modify the conf/server.xml
2. Issue a JMX command to provision the new virtual host in the running Tomcat

You might also want to consider having separate Tomcat instances per domain. That might be
more manageable, though it will require more memory on your server(s).

- -chris
Comment: GPGTools -
Comment: Using GnuPG with Thunderbird -


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

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

View raw message