3 Replies Latest reply on Nov 13, 2012 11:49 AM by Radoslav Husar

    LoadBalancePolicy  on JBoss AS7.1

    Saravanan Muthusamy Newbie

      Hello,

       

      How do I configure the LoadBalancePolicy(on JBoss AS 7.1) for all RMI invocations, neither i can find the document nor subsystem explaining (configuration) details on how RMI load or failover has been handled on JBoss 7.

       

      JBoss 5.1 had jmx-invoker-service.xml deployment where we can configure the LoadBalancePolicy to distribute/failover the RMI calls made from my standalone client.

       

      Can some one point me the URL explaining these details specific to JBoss AS7?.

      Thanks a lot.

        • 1. Re: LoadBalancePolicy  on JBoss AS7.1
          Wolf-Dieter Fink Master

          The behavior changed in AS7. There is no (proxy)class download as in AS5.

          Therefor the configuration will be done at client side.

           

          You might add one or more servers to the configuration, dee this document.

          If the servers are clustered you can add the functionality of auto detection by adding this:

          remote.clusters=ejb

          remote.cluster.ejb.connect.options.org.xnio.Options.SSL_ENABLED=false

          # maybe authentication

          remote.cluster.ejb.username=user

          remote.cluster.ejb.password=mypassword

          • 2. Re: LoadBalancePolicy  on JBoss AS7.1
            Saravanan Muthusamy Newbie

            Thanks Wolf-Dieter Fink.

             

            I want my client to do a jmx based RMI invocation. is there is a way my client can dynamically update the currently available servers and balances load based on the current list in a cluster group?. should i add all these support in my app?

            • 3. Re: LoadBalancePolicy  on JBoss AS7.1
              Radoslav Husar Master

              . is there is a way my client can dynamically update the currently available servers and balances load based on the current list in a cluster group?

              This is done automatically by the client. In your static configuration you only specify list of initial nodes to connect to, after the first request, the list will be updated with the current cluster state. You however need to configure authentication to use with these nodes.

               

              Rado