2 Replies Latest reply on Aug 11, 2011 7:56 AM by guiye

    jboss 5.1.0 GA farm clustering HA

    guiye Newbie



      i've used jboss 5.1.0 GA for an application on my company, but now we need to make hot deploys, so we can't have the application down by minutes...


      so, i decided to make a farm of two nodes...


      node1: run.bat -c node1 -g DocsPartition -u -Djboss.messaging.ServerPeerID=1 -Djboss.service.binding.set=ports-01

      node2: run.bat -c node2 -g DocsPartition -u -Djboss.messaging.ServerPeerID=2 -Djboss.service.binding.set=ports-02


      both application & works good. i've deployed the EAR file on node1/farm dir and it was deployed on both nodes.


      but, I want to make a "hot deploy", what i mean the application should be available all the time:


      an deployment example: first deploy on node1 (without stopping node2), when node1 is 100% deployed  & started, then deploy on the node2...  what i want is high availability... right?


      i'm using the "all" configuration... how can I do this? is this possible? or I should not use farm and make the deployment manually?


      also, how could I do that in jboss 7?

        • 1. Re: jboss 5.1.0 GA farm clustering HA
          Paul Ferraro Master

          From what I can tell from you're question, you want a load balancer in front of your application servers, i.e. a single point of entry that will direct requests to an application server, while being smart enough not to direct to a server in the process of re-deploying the application.  If you use mod_cluster for load balancing, then you'll be able to retain availability during hot re-deployment.  You'll want to make sure your application is configured with distributed web sessions and clustered SFSBs (if needed).  See the docs for details:



          If that wasn't the essence of your inquiry, please restate your question.

          • 2. Re: jboss 5.1.0 GA farm clustering HA
            guiye Newbie

            Thanks Paul for your answer.


            Yes, I'll use httpd with mod_cluster in the front.


            Let's suppose that I have two nodes running in farm mode: I want to make a hot deploy with farm, both nodes will redeploy at the same time, so the application would be offline a few minutes until one node is available, right?


            I cant allow that, I need to have one node available.


            An option is to not use farm, and deploy each node manually: deploy node1, wait to see it restarted, then deploy node2, etc.


            My question is, can farm do this "secuential deployment" for me?