I do mean mod_jk2. Could this be the problem? /roberto ----- Original Message ----- From: "Peter Rossbach" <[EMAIL PROTECTED]> To: "Tomcat Users List" <tomcat-user@jakarta.apache.org> Sent: Saturday, January 29, 2005 10:42 PM Subject: Re: Updating webapps in a running production cluster.
Please update to Apache 2.0.52 and I hope you mean mod_jk 1.2.8 not a mod_jk2 Regards Peter Roberto Cosenza schrieb: >We used : >jakarta-tomcat-5.5.4 >apache 2.0.49 >mod_jk2 (jakarta-tomcat-connectors-1.2.8-src) >Linux webster2 2.4.26 #11 SMP Thu Apr 22 13:16:46 CEST 2004 i686 i686 i386 >GNU/Linux >jdk-1_5_0_01-linux-i586.bin >CATALINA_OPTS='-Xmx512m -Xms256m -XX:MaxPermSize=256M' > >I will test a new version and let you know. > >----- Original Message ----- >From: "Peter Rossbach" <[EMAIL PROTECTED]> >To: "Tomcat Users List" <tomcat-user@jakarta.apache.org> >Sent: Saturday, January 29, 2005 8:04 PM >Subject: Re: Updating webapps in a running production cluster. > > >Hello, > >with which tomcat version you test this, please try the new 5.5.7 and >tell us the result! :-) >Please tell us your env, Apache, mod_jk JDK, OS > >Thanx >Peter > >PS: You can find my cluster dev template at >http://tomcat.objektpark.org/examples/05_02_tomcat_example.tar.gz, >Sorry the docs are german and it works with tomcat 5.5.5m jdk 5, apache >2.0.52, mod_jk 1.2.8 on Windows/Linux > >Roberto Cosenza schrieb: > > > >>Sorry if I insist with this post. >>Has anybody succeeded in updating a webapp in a tomcat cluster without >>loosing (any)requests? >>Iīm wondering if this is possible at all with tomcat. >>If we donīt provide a solution we are forced to switch to an other servlet >>container :-(((( >>Does anybody know if moving to Jboss, with tomcat as a servlet container, >>will help? >> >>Thanx >>----- Original Message ----- >>From: "Roberto Cosenza" <[EMAIL PROTECTED]> >>To: "Tomcat Users List" <tomcat-user@jakarta.apache.org> >>Sent: Thursday, January 20, 2005 8:59 PM >>Subject: Re: Updating webapps in a running production cluster. >> >> >> >> >> >> >>>We have done some testing in this direction. >>>Two tomcat in a cluster, with session replication. >>>Shutdown B, update B, restart B >>>Shutdown A, update A, restartAB >>> >>>What we experience is that, when shutting down any of the two servers. >>>1) Few requests are lost (let's say, on our machine, for 0.30 seconds?) >>>2) Objects stored in the session disappear temporarly, causing eventually >>>annoing npe's. >>>We were wondering if it is possible to achieve an higher reliability but >>> >>> >>> >>> >>we >> >> >> > > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
