Maven And Load Balancing deployment
Hello everybody, Im 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 doesnt 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 its being redeployed? Thanks in advance, Stéphane
Re: Maven And Load Balancing deployment
--- 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]
Re: Maven And Load Balancing deployment
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]
RE: Maven And Load Balancing deployment
Thanks a lot, I used the jkstatus and added url calls in my deployment process. Everything works fine, my app is now available even while I'm redeploying it Stéphane -Message d'origine- De : Rainer Jung [mailto:[EMAIL PROTECTED] Envoyé : lundi 22 octobre 2007 17:16 À : Tomcat Users List Objet : Re: Maven And Load Balancing deployment 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, Im 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 doesnt 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 its 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] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven And Load Balancing deployment
Great. If you want to improve our documentation, feel free to open a bugzilla issue and attach some text. Stéphane Hanser wrote: Thanks a lot, I used the jkstatus and added url calls in my deployment process. Everything works fine, my app is now available even while I'm redeploying it Stéphane -Message d'origine- De : Rainer Jung [mailto:[EMAIL PROTECTED] Envoyé : lundi 22 octobre 2007 17:16 À : Tomcat Users List Objet : Re: Maven And Load Balancing deployment 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]
