Hello list,
I have two instances of Tomcat running the same webapp behind a load
balancer. My current redeployment method is just simply shut one instance
down(undeploy), replace warfile, deploy latest war back online, and then
proceed to the seond instance.
This works most of the time, but for
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
Hi Mark,
How do you - disable worker1 and still let Tomcat1 to process remaining
requests? I guess I am not sure what worker1 is, where to disable that.
Can you explain little more on this?
Yes, I have heard of LambdaProbe. I will check this out in more detail
later.
Thanks for sharing.
-Z
On
Zemian Deng wrote:
Hi Mark,
How do you - disable worker1 and still let Tomcat1 to process remaining
requests? I guess I am not sure what worker1 is, where to disable that.
Can you explain little more on this?
I was assuming you were using httpd and mod_jk or mod_proxy_ajp to do the
load
