7 Replies Latest reply on Jul 28, 2003 11:43 AM by Kevin

    Configuration for JBoss Clustering

    monasehgal Newbie

      I have 2 jboss servers running at two windows m/c .I would appereciate if any body can guide me with configuring Jboss clustering.Right now my application is in /default. Any reference to any documentation would be helpful

        • 1. Re: Configuration for JBoss Clustering
          Darran Lofthouse Master

          The JBoss documentation needs to be bought, there should be a link to the right of the page.

          JBoss does come ready to run clustered without any changes.

          If you install JBoss on two machines and on both machines start JBoss with run -c all instead of just run they will start with the all configuration which if there are no problems should result in you having two nodes in a single cluster.

          There is too much really to go into on here, the documentation covers trouble shooting, settings for Windows and details on how to configure and use your application in a clustered environment.

          • 2. Re: Configuration for JBoss Clustering
            Kevin Newbie

            Make sure in your cluster-config.xml that you have the loopback="true" option set if you are running on Windows.

            If you take the same 3.2.2RC1 version of Jboss, on two windows machines and do what darran1 said, after you see in each console window the ... Started.. at the end, scroll up somwhere near the middle you'll see something like:

            ****************************************
            GMS: address is xxx:2820
            *****************************************
            [ClusterPartition] Starting channel..

            and so forth. Look at BOTH of them at this location. See if one says Number of cluster memebers: 2, and one would say 1 (presumably the first one you started).

            As long as you have not put in ANY beans or anything, and just ran it right out of the unzipped dir with the -c all config, you should have no problems. If you do, you either don't have loopback="true" for windows, or possibly multi-cast is not working. Run the JavaGroups test on both machines to confirm multi-cast works. IF that works, then you should have no other problem, as long as the computers are in the same subnet and network range.

            • 3. Re: Configuration for JBoss Clustering
              monasehgal Newbie

              Thanks a lot
              That's a big help

              • 4. Re: Configuration for JBoss Clustering
                monasehgal Newbie

                Got the documentation Read it. It's quite helpful
                Thanx

                • 5. Re: Configuration for JBoss Clustering
                  monasehgal Newbie

                  hi
                  I made all the necessary changes as mentioned in the documentation but i receive the following error can anyone pls help

                  .......
                  .......
                  2003-07-22 23:48:11,091 INFO [org.jboss.naming.NamingService] Starting jnp server
                  2003-07-22 23:48:11,261 DEBUG [org.jboss.naming.NamingService] NamingServer stub: org.jnp.server.NamingServer_Stub[RemoteStub [ref: [endpoint:[192.168.0.101:1606](local),objID:[0]]]]
                  2003-07-22 23:48:11,321 INFO [org.jboss.naming.NamingService] Started jnpPort=1099, rmiPort=0, backlog=50, bindAddress=null, Client SocketFactory=null, Server SocketFactory=null
                  2003-07-22 23:48:11,361 DEBUG [org.jboss.naming.NamingService] InitialContext Environment:
                  2003-07-22 23:48:11,361 DEBUG [org.jboss.naming.NamingService] key=java.naming.provider.url, value=server1:1100,server2:1100
                  2003-07-22 23:48:11,361 DEBUG [org.jboss.naming.NamingService] key=java.naming.factory.initial, value=org.jnp.interfaces.NamingContextFactory
                  2003-07-22 23:48:11,361 DEBUG [org.jboss.naming.NamingService] key=java.naming.factory.url.pkgs, value=org.jboss.naming:org.jnp.interfaces
                  2003-07-22 23:48:11,361 WARN [org.jboss.naming.NamingService] Context.PROVIDER_URL in server jndi.properties, url=server1:1100,server2:1100
                  2003-07-22 23:48:11,421 INFO [org.jboss.naming.NamingService] Listening on port 1099
                  2003-07-22 23:48:11,431 INFO [org.jboss.naming.NamingService] Started
                  2003-07-22 23:48:11,441 INFO [org.jboss.naming.JNDIView] Starting
                  2003-07-22 23:48:11,451 INFO [org.jboss.naming.JNDIView] Started
                  2003-07-22 23:48:11,451 DEBUG [org.jboss.system.ServiceController] waiting in start jboss:service=HAJNDI on jboss:service=MyPartition
                  2003-07-22 23:48:11,451 INFO [org.jboss.security.plugins.SecurityConfig] Starting
                  2003-07-22 23:48:11,461 DEBUG [org.jboss.security.plugins.SecurityConfig] Installed JAAS Configuration service=jboss.security:name=XMLLoginConfig, config=org.jboss.security.auth.login.XMLLoginConfig@2af0b3
                  2003-07-22 23:48:11,461 INFO [org.jboss.security.plugins.SecurityConfig] Started
                  2003-07-22 23:48:11,661 INFO [org.jboss.security.plugins.JaasSecurityManagerService] Starting
                  2003-07-22 23:48:11,671 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] securityMgrCtxPath=java:/jaas
                  2003-07-22 23:48:11,671 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] cachePolicyCtxPath=java:/timedCacheFactory
                  2003-07-22 23:48:11,681 DEBUG [org.jboss.security.plugins.JaasSecurityManagerService] SecurityProxyFactory=org.jboss.security.SubjectSecurityProxyFactory@42552c
                  2003-07-22 23:48:11,681 INFO [org.jboss.security.plugins.JaasSecurityManagerService] Started
                  2003-07-22 23:48:11,691 INFO [org.jboss.tm.TransactionManagerService] Starting
                  2003-07-22 23:48:11,782 INFO [org.jboss.tm.TransactionManagerService] Started
                  2003-07-22 23:48:11,792 INFO [org.jboss.tm.usertx.server.ClientUserTransactionService] Starting
                  2003-07-22 23:48:22,527 ERROR [org.jboss.tm.usertx.server.ClientUserTransactionService] Starting failed
                  javax.naming.CommunicationException: Receive timed out. Root exception is
                  java.io.InterruptedIOException: Receive timed out
                  at java.net.PlainDatagramSocketImpl.receive(Native Method)
                  at java.net.DatagramSocket.receive(DatagramSocket.java:387)
                  at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:919)
                  at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:997)
                  at org.jnp.interfaces.NamingContext.bind(NamingContext.java:388)
                  at org.jnp.interfaces.NamingContext.bind(NamingContext.java:381)
                  at javax.naming.InitialContext.bind(InitialContext.java:353)
                  at org.jboss.tm.usertx.server.ClientUserTransactionService.startService(ClientUserTransactionService.java:73)
                  at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:162)
                  at java.lang.reflect.Method.invoke(Native Method)
                  at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
                  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
                  at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:894)
                  at $Proxy0.start(Unknown Source)
                  at org.jboss.system.ServiceController.start(ServiceController.java:340)
                  at java.lang.reflect.Method.invoke(Native Method)
                  at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
                  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
                  at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
                  at $Proxy3.start(Unknown Source)
                  at org.jboss.deployment.SARDeployer.start(SARDeployer.java:243)
                  at org.jboss.deployment.MainDeployer.start(MainDeployer.java:678)
                  at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:513)
                  at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:481)
                  at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:465)
                  at java.lang.reflect.Method.invoke(Native Method)
                  at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
                  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
                  at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:314)
                  at org.jboss.system.server.ServerImpl.start(ServerImpl.java:216)
                  at org.jboss.Main.boot(Main.java:142)
                  at org.jboss.Main$1.run(Main.java:375)
                  at java.lang.Thread.run(Thread.java:479)
                  2003-07-22 23:50:01,519 ERROR [org.jboss.deployment.SARDeployer] start operation failed on package file:/C:/jboss/jboss-3.0.0_tomcat-4.0.3/server/all/conf/jboss-service.xml
                  javax.naming.CommunicationException: Receive timed out. Root exception is
                  java.io.InterruptedIOException: Receive timed out
                  ........
                  .......

                  • 6. Re: Configuration for JBoss Clustering
                    Sacha Labourey Master

                    the version you are using (3.0.0) is more than 15 months old!!! Upgrade to 3.2.2Rc2 or 3.0.8.

                    Cheers,

                    sacha

                    • 7. Re: Configuration for JBoss Clustering
                      Kevin Newbie

                      It helps to post versions of things. Had I seen the 3.0.0 in your post, I would have told you to make sure to go to 3.2.2RC1/2 or at least 3.2.1. Even so I mention in my post using 3.2.2RC. Make sure you look out for these types of things, it will help you avoid problems.