You can tell the mod_jk load balancer to disable or stop workers
temporarily via a status worker. There is a docs page for the status
worker, which also describes the URL structure.
We also have an ant task "jkstatus", that can be used to combine ant
with the mod_jk status worker. There might be small functional gaps
between the status worker and the jkstatus ant task, because the status
worker had some big improvements a while ago, and jkstatus is in the
process of catching up.
Regards,
Rainer
Stéphane Hanser wrote:
Hello everybody,
I’m currently working on a webapp using tomcat as application server. As we
got a lot of users and the server was not able to handle them all alone, we
run 2 instances of tomcat and we use load balancing through a
workers.properties file in apache2 directory.
I need to redeploy my application often and I would like to make it without
cutting the access to users. In order to do that, I use maven to redeploy
the application on each instance, one after the other.
This works fine but the load balancer doesn’t detect that an instance is
being unavailable and still tries to redirect to it (and it displays a blank
page).
So here is my question: is there a way for the load balancer to detect that
it should not use one instance the time it’s being redeployed?
Thanks in advance,
Stéphane
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
