Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 17543 invoked from network); 7 Jun 2006 19:57:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 Jun 2006 19:57:36 -0000 Received: (qmail 97478 invoked by uid 500); 7 Jun 2006 19:57:24 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 97041 invoked by uid 500); 7 Jun 2006 19:57:22 -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 97030 invoked by uid 99); 7 Jun 2006 19:57:22 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Jun 2006 12:57:22 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [129.196.250.12] (HELO dhrseasvgw01.danahermail.com) (129.196.250.12) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Jun 2006 12:57:20 -0700 Received: from dhrseasvxf01.messaging.danaherad.com (dhrseasvxf01.messaging.danaherad.com [172.29.152.75]) by dhrseasvgw01.danahermail.com (BorderWare MXtreme Mail Firewall) with ESMTP id 3795E8F2EC for ; Wed, 7 Jun 2006 12:56:54 -0700 (PDT) Received: from dhrseasvxb01.messaging.danaherad.com ([172.29.152.77]) by dhrseasvxf01.messaging.danaherad.com with Microsoft SMTPSVC(6.0.3790.2499); Wed, 7 Jun 2006 12:24:14 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Webapp Reload Date: Wed, 7 Jun 2006 12:24:13 -0700 Message-ID: <24D874BD2FF1CB4793BB914F2F29E59B0146F7A4@dhrseasvxb01.messaging.danaherad.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Webapp Reload Thread-Index: AcaKXLvadM3gpufQROiuDwSpql3o+AAB2xug From: "Asensio, Rodrigo" To: "Tomcat Users List" X-OriginalArrivalTime: 07 Jun 2006 19:24:14.0871 (UTC) FILETIME=[F6836A70:01C68A67] X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Thanks for the answer. Filip, I will try some solutions with your clues. Thanks -----Original Message----- From: Filip Hanik - Dev Lists [mailto:devlists@hanik.com]=20 Sent: Wednesday, June 07, 2006 2:03 PM To: Tomcat Users List Subject: Re: Webapp Reload yes, login information is not preserved during a restart/reload. you would have to come up with a custom solution for this, possible just creating a simple extension to the StandardManager or do it within your application using another session attribute and a filter Filip Marc Farrow wrote: > Things brings up an interesting point. How do you make the standard=20 > tomcat session attributes Serializable? Because, I currently am using > a security constraint against an LDAP server. However, every time I=20 > redeploy the application the session is lost. > > On 6/7/06, Filip Hanik - Dev Lists wrote: >> >> My guess is that your session attributes do not implement=20 >> java.io.Serializable >> >> if they don't tomcat can not store them for a restart or reload Filip >> >> >> >> Asensio, Rodrigo wrote: >> > Hello, >> > We have a call center webapp with 100 simultaneous sessions all >> > time ( 24/7 ). This webapp has several sections that are updated with >> > new JSPs or Java Classes like 3 times a week. >> > Each time that we need update the webapp all users loose their=20 >> sessions. >> > This is a big problem all time. Our solution was create a mirror=20 >> server. >> > Then, each time that we need update server#1, everybody moves to=20 >> #2. But >> > this solution I don't like at all. >> > >> > If I have to update just JSPs there is no problem. But the big=20 >> issue is >> > if I have to change class files. They do not take effect until next >> > tomcat restar or webapp reload. >> > >> > Is there any way to avoid this ? Like a replace classes in the >> > classloader ? Or load dinamically new classes ? >> > >> > Thanks all. >> > >> > ------------------------------------------------------------------- >> > Rodrigo Asensio >> > Fuel Management Services >> > Gilbarco Veeder Root >> > phone: +1 336 547 5023 >> > email: rodrigo.asensio@gilbarco.com >> > >> > This message (including any attachments) contains confidential >> > and/or proprietary information intended only for the addressee. >> > Any unauthorized disclosure, copying, distribution or reliance on >> > the contents of this information is strictly prohibited and may >> > constitute a violation of law. If you are not the intended >> > recipient, please notify the sender immediately by responding to >> > this e-mail, and delete the message from your system. If you >> > have any questions about this e-mail please notify the sender >> > immediately. >> > >> > --------------------------------------------------------------------- >> > To start a new topic, e-mail: users@tomcat.apache.org >> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org >> > For additional commands, e-mail: users-help@tomcat.apache.org >> > >> > >> > >> > >> >> >> --=20 >> >> >> Filip Hanik >> >> --------------------------------------------------------------------- >> To start a new topic, e-mail: users@tomcat.apache.org >> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org >> For additional commands, e-mail: users-help@tomcat.apache.org >> >> > > > ------------------------------------------------------------------------ > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.394 / Virus Database: 268.8.2/357 - Release Date: 6/6/2006 > =20 --=20 Filip Hanik --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org This message (including any attachments) contains confidential and/or proprietary information intended only for the addressee. Any unauthorized disclosure, copying, distribution or reliance on the contents of this information is strictly prohibited and may constitute a violation of law. If you are not the intended recipient, please notify the sender immediately by responding to this e-mail, and delete the message from your system. If you have any questions about this e-mail please notify the sender immediately. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org