---------------------------------------------------------------------------
HARBOR: http://coolharbor.100free.com/index.htm
Now Tomcat is also a cool application server
---------------------------------------------------------------------------
----- Original Message -----
From: "Stéphane Hanser" <[EMAIL PROTECTED]>
To: <users@tomcat.apache.org>
Sent: Monday, October 22, 2007 3:53 PM
Subject: Maven And Load Balancing deployment
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.
=====================================
I dont know maven...
What I do is use ant script to deploy TC, its built into TC already.
If you download the Deployment Package (think thats the name), you'll figure
it out.
Thats all I use, but I know I'm naughty and should use JKStatus to stop the
relevent server first.
So I think what one shoud really do is, stop the server in JKStatus, run ant
script for that server (or maven)... continue etc etc.
Good luck...
=================================================
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]
