Hi,
I'm running a tomcat that provides services for a lot of clients.
Each "client" one has a number of services (via axis) on their "own"
context. Now I'm migratingto a bigger machine, and I got the doubt: is
it better (for performance) to "group as many services as possible by
context", or hav
From a performance point of view - it doesn't matter.
From a maintenaince point of view - I prefer many lean clients. That way -
if one of them behaves badly - off they go into a new JVM (assuming you have
apache in front of tomcat)
-Tim
Javier Gonzalez wrote:
Hi,
I'm running a tomcat
Actually, I don't - this server provides web services only and *very
small* set of reports pages, so going through the hassle of setting up
Apache in front of tomcat wasn't deemed to be worth it.
It doesn't have any impact on performance? I would have thought that
multiple contexts would eventual
Duplicate libraries wasting some extra memory is a tiny penalty compared to
being trapped, unable to upgrade web service when another service relies on
the same library(and is incompatible with newer versions). (Or replace
service with webapp)
-Tim
Javier Gonzalez wrote:
Actually, I don't
