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.
weWe 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
updidn not succeed. /roberto
----- Original Message ----- From: "Derrick Koes" <[EMAIL PROTECTED]> To: "Tomcat Users List" <tomcat-user@jakarta.apache.org> Sent: Thursday, January 20, 2005 8:46 PM Subject: RE: Updating webapps in a running production cluster.
This is how we update apps in time critical situations. Shut one down and
update. Bring it back up. Shut the next down and update. Bring it back
and so on.
--------------------------------------------------------------------- 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]
