tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject RE: Switching between releases during runtime
Date Tue, 08 Apr 2003 18:49:29 GMT
Hi Filip,

Thx for your idea, opening up a new horizon of options for HA!
However, it seems clustering is still beta in Tomcat 4.x --- have you 
found it to work smoothly?

And what happens if you update one member of the cluster with a new app?
Is it possible to first redirect traffic from the IP-addresses of 
testing-PCs to the member with the new app and after successful tests 
redirect to the new member and update the others step by step?
Do you have any tips for how to update a webapp in a cluster while 
guaranteeing consistency of the application interface to the enduser (= 
only one version active at a time)?

thx alot

"Filip Hanik" <> 
08.04.2003 19:56
Please respond to
"Tomcat Users List" <>

"Tomcat Users List" <>

RE: Switching between releases during runtime

the easier way to achieve HA is to cluster your servers,
that way you can take one server down, upgrade it, and then launch it 
without loosing data
take a look at


> -----Original Message-----
> From: Shapira, Yoav []
> Sent: Tuesday, April 08, 2003 10:54 AM
> To: Tomcat Users List
> Subject: RE: Switching between releases during runtime
> Howdy,
> >My issue relates heavily to the "High availability Tomcat webapps using
> >ant undeploy/deploy??" question I posted as well.
> I figured ;)
> ># create symlink
> >ln -s myapp-1.0 myapp # create a symlink to point to myapp
> >==> http://localhost:8080/myapp first gives a 404 not found. After a
> while
> >(probably after Tomcat has created /work/Standalone/localhost/myapp
> with
> >the contents of myapp-1.0) it works as expected.
> Did you investigate the allowSymlink attribute (or whatever the precise
> name) of the <Context> element in server.xml?
> >Don't you think this would be a great thing to have in production? No
> >downtime means no lost visitors!!
> Actually I think it's an atrocious idea.  Testing of a release should be
> done on a test server simulating production environment and load as
> closely as possible.  Then the releases should be swapped with minimal,
> but nonzero, down-time.  A new release is a significant event.  The
> production server is not the place to do testing.
> Yoav Shapira
> Millennium ChemInformatics
> This e-mail, including any attachments, is a confidential
> business communication, and may contain information that is
> confidential, proprietary and/or privileged.  This e-mail is
> intended only for the individual(s) to whom it is addressed, and
> may not be saved, copied, printed, disclosed or used by anyone
> else.  If you are not the(an) intended recipient, please
> immediately delete this e-mail from your computer system and
> notify the sender.  Thank you.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message