Cavallotti 16 - 20089, Rozzano - Milano - ITALY
http://www.sonicle.com
--
Da: Christopher Schultz
A: Tomcat Users List
Data: 9 luglio 2010 3.01.37 CEST
Oggetto: Re: Updating webapps classes
-BEGIN PGP SIGNED MESSAGE
=-
--
Da: Christopher Schultz
A: Tomcat Users List
Data: 9 luglio 2010 3.01.37 CEST
Oggetto: Re: Updating webapps classes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gabriele,
On 7/7/2010 8:11 AM, Gabriele Bulfon wrote:
I get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gabriele,
On 7/7/2010 8:11 AM, Gabriele Bulfon wrote:
I get back to this discussion beacuse I was brainstorming again on it,
and found
that the already present class loader may actually be able to do this alone.
My thought was: if Tomcat is
--
Da: Christopher Schultz
A: Tomcat Users List
Data: 3 maggio 2010 15.57.57 CEST
Oggetto: Re: Updating webapps classes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
On 4/30/2010 10:33 AM, Peter Crowther wrote:
In normal use, Tomcat1
028243880
Via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALY
http://www.sonicle.com
--
Da: Peter Crowther
A: Tomcat Users List
Data: 30 aprile 2010 16.33.39 CEST
Oggetto: Re: Updating webapps classes
It's very
Gabriele Bulfon wrote:
Hi, thanx for the interesting solution.
Anyway, not always possible to run 2 tomcat instances because of memory
requirements.
Do you see any different solution with 1 tomcat only (or tomcat + apache)?
Gabriele,
I think Peter gave you the only appropriate general answer.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
On 4/30/2010 10:33 AM, Peter Crowther wrote:
In normal use, Tomcat1 is running. The load balancer directs all users to
Tomcat1. Tomcat2 could even be stopped.
I would say that normal use would include both (or however many)
instances
Hello,
I don't know if I'm asking something stupid, but I'm investigating this for
days, and found
nothing around.
Updating a java webapp can be a problem when this java webapp is being ised
24/7 by users,
and many of them have sessions running for all the working hours.
Consider that this
It's very hard to do this using one Tomcat instance. It's very easy to do
this using two Tomcat instances (call them Tomcat1 and Tomcat2) and a load
balancer (Apache httpd should be fine for this job).
In normal use, Tomcat1 is running. The load balancer directs all users to
Tomcat1. Tomcat2
