Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 86573 invoked from network); 3 May 2010 07:12:13 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 May 2010 07:12:13 -0000 Received: (qmail 28809 invoked by uid 500); 3 May 2010 07:12:09 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 28569 invoked by uid 500); 3 May 2010 07:12:09 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 28560 invoked by uid 99); 3 May 2010 07:12:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 07:12:08 +0000 X-ASF-Spam-Status: No, hits=4.5 required=10.0 tests=AWL,HTML_MESSAGE,RCVD_NUMERIC_HELO,SPF_PASS,TWO_IPS_RCVD X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [217.133.203.66] (HELO www.sonicle.com) (217.133.203.66) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 07:12:03 +0000 Received: from localhost (localhost [127.0.0.1]) by www.sonicle.com (Postfix) with ESMTP id 9F84ABC298 for ; Mon, 3 May 2010 09:10:40 +0200 (CEST) Received: from www.sonicle.com ([127.0.0.1]) by localhost (www [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 04965-08 for ; Mon, 3 May 2010 09:10:36 +0200 (CEST) Received: from 192.165.1.243 (pgbulfon.sonicle.com [192.168.222.10]) by www.sonicle.com (Postfix) with ESMTP id E95FEBC26D for ; Mon, 3 May 2010 09:10:35 +0200 (CEST) Date: Mon, 3 May 2010 09:11:29 +0200 (CEST) From: Gabriele Bulfon To: Tomcat Users List Message-ID: <27575732.2.1272870689851.JavaMail.gbulfon@pgbulfon> Subject: Re: Updating webapps classes MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_0_32788167.1272870689841" X-Virus-Scanned: amavisd-new at sonicle.com ------=_Part_0_32788167.1272870689841 Content-Type: multipart/alternative; boundary="----=_Part_1_6302571.1272870689842" ------=_Part_1_6302571.1272870689842 Content-type: text/plain Content-Transfer-Encoding: 7bit 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)? Thx in advance, Gabriele. Gabriele Bulfon - Sonicle S.r.l. Tel +39 028246016 Int. 30 - Fax +39 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 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 could even be stopped. To upgrade, you upgrade Tomcat2 (and start it if needed) and tell the load balancer that new sessions should be sent to Tomcat2. Once all user sessions are off Tomcat1, you upgrade it and tell the load balancer to direct new sessions to Tomcat1. Once all user sessions are off Tomcat2, you can shut it down again or leave it running for fault tolerance. If you have enough RAM on your server (and the load is low enough), you could even run all three of Tomcat1, Tomcat2 and httpd on the same server. Does this help? - Peter On 30 April 2010 14:46, Gabriele Bulfon wrote: 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 webapp consists of many instance classes being created during session startup. How can I manage updates of the webapp classes without having to reload the webapp? What I would like is that users inside the application to continue to see the old version, while new ones logging in would see the latest one. I don't know if there is any way for this.... Thanks Gabriele. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org ------=_Part_1_6302571.1272870689842 Content-type: text/html Content-Transfer-Encoding: quoted-printable
Hi, thanx for the int= eresting 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)?
Thx in advance,
Gabriele.

Gabriele Bulfon - Sonicle S.r.l.
Tel +39 028246016 Int. 30 - Fax +39 028243880
Via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALY
http://www.sonicle.com



-------------------------------------= ---------------------------------------------

Da: Peter Crowther <= ;peter.crowther@melandra.com>
A: Tomcat Users List <users@tomcat.a= pache.org>
Data: 30 aprile 2010 16.33.39 CEST
Oggetto: Re: Updati= ng webapps classes

It's very har= d to do this using one Tomcat instance. It's very easy to do
this u= sing two Tomcat instances (call them Tomcat1 and Tomcat2) and a load
bal= ancer (Apache httpd should be fine for this job).

In normal use, Tom= cat1 is running. The load balancer directs all users to
Tomcat1. Tomca= t2 could even be stopped.
To upgrade, you upgrade Tomcat2 (and start it = if needed) and tell the load
balancer that new sessions should be sent t= o Tomcat2.
Once all user sessions are off Tomcat1, you upgrade it and te= ll the load
balancer to direct new sessions to Tomcat1.
Once all user= sessions are off Tomcat2, you can shut it down again or leave
it runnin= g for fault tolerance.

If you have enough RAM on your server (and th= e load is low enough), you
could even run all three of Tomcat1, Tomcat2 = and httpd on the same server.

Does this help?

- Peter

= On 30 April 2010 14:46, Gabriele Bulfon <gbulfon@sonicle.com> wrote:<= br>
> Hello,
> I don't know if I'm asking something stu= pid, but I'm investigating this for
> days, and found
> not= hing around.
>
> Updating a java webapp can be a problem when t= his java webapp is being ised
> 24/7 by users,
> and many of th= em have sessions running for all the working hours.
> Consider that t= his webapp consists of many instance classes being created
> during s= ession startup.
> How can I manage updates of the webapp classes with= out having to reload the
> webapp?
> What I would like is that = users inside the application to continue to see
> the old version,> while new ones logging in would see the latest one.
>
> I= don't know if there is any way for this....
> Thanks
> Gab= riele.
>
>
>
>
> ----------------------------= -----------------------------------------
> To unsubscribe, e-mail: u= sers-unsubscribe@tomcat.apache.org
> For additional commands, e-mail:= users-help@tomcat.apache.org
>




= ------=_Part_1_6302571.1272870689842-- ------=_Part_0_32788167.1272870689841 Content-Type: text/plain; charset=us-ascii --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org ------=_Part_0_32788167.1272870689841--