On 30.10.2018 08:13, Ahmed, Tarek wrote:
Thanks for your input!
To summarize: Most of us seem to prefer not to have too many web
applications running in one tomcat instance. If, however, it is possible
to run a tomcat with many applications in a stable way it reduces
administrative overhead to do so. The prerequisites for this are that
the applications are mature, handle resources well and don't get too
many updates (we _do_ regular dependency updates, though ...).
On the other hand, if there is - for whatever reason - a regular need of
restarts or re-deployments or if the applications deployed need
individual monitoring or special care or whatever, there is a case for
one application per tomcat.
What do I make of this? There might be a compromise here: Identify those
applications that don't cause trouble and put them into one tomcat
instance. Everything else (new applications, buggy ones no one bothers
to fix anymore, applications that get regular feature updates etc.) are
isolated in their own tomcat instances. As soon as those become stable
we can move them to (one of) the fat tomcat(s).
Sounds like something I might get through :-)
And somehow, this sounds a lot like Java GC. It should be possible to automate
this..
Thanks and greetings,
tarek
Am 29.10.18 um 09:00 schrieb Ahmed, Tarek:
Hi all,
TLDR? Do you deploy one web application per tomcat instance or several?
[...]
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
