On Mon, Mar 10, 2014 at 9:03 AM, Daniel Mikusa <dmik...@gopivotal.com>wrote:
> On Mar 9, 2014, at 11:05 AM, Neven Cvetkovic <neven.cvetko...@gmail.com>
> wrote:
> > Thus, if you run multiple instances of Tomcat - alone, virtual hosting
> will
> > not help you , since only one process can bind to a single IP address to
> > one port (e.g. port 80). So, either put everything to the same Tomcat
> > ("yuck"),
>
> Just wanted to point out that there is nothing wrong with this approach.
> There are cases where it is a good idea. One example would be when
> running lots of small sites. There is overhead for running an each JVM and
> Tomcat instance. If you have a large number of small sites, it might makes
> sense to combine them into one or a few Tomcat instances to reduce that
> overhead.
>
> Dan
>
>
+1. Dan, that's a great use case for single instance Tomcat. However, keep
in mind - in the ideal world, where we have infinite amount of resources
(staff, hardware, electricity, memory, etc...) - you would want each
application on its own Tomcat instance, and we generally make apps coexist
on the same Tomcat instance for optimization purposes (reducing hardware to
manage, reducing staff to support various instances, preserving
electricity, etc...)
Another example that I've seen is to have a single instance, with a single
application - but hosted for various domains, with some dynamic
white-labeling application, e.g. webmail client, mailing list software,
etc...
