Zemian Deng wrote:
Can you share your story of how you solve your redeployment problem to keep
max availability of your webapp?
1. Write stateless apps and where you can't, use sticky sessions and
clustering.
2. When upgrading. I:
- disable worker1
- wait for all requests on Tomcat 1 to complete (LambdaProbe is great for
monitoring this and a bunch of other stuff)
- upgrade Tomcat 1
- enable worker 1
- repeat for worker 2
Using this approach I never had any downtime associated with an upgrade.
There were plenty of other causes of downtime ;), but upgrade wasn't one of
them.
Mark
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
