4 Replies Latest reply on May 3, 2005 2:02 AM by Ben Wang

    2 jboss instances clustered using same server

    Alessandro Behling Newbie

      Hi,

      If someone could give a hand on this:

      I need to set up an environment which needs to attend a live clustered JBoss (tha is already running) and live and another one completely different that we are going to use as staging, but even for staging, it needs to be clustered
      (customer requirements).

      I've copied the 'all' folder into a new one, and changed some properties accordingly the 'JBoss Clustering' doc I've got from the docs section here in the JBoss web site. The settings I've changed are related with the partition name, because I want to get my 'staging' environment in a different partition than 'DefaultPartition' defined in the original conf files

      So far, I've got only the live one working fine, and it was quite easy to setup. My problem started when I tried to configure the second one, I'm getting conflicts between the JNDI ports. It says that that port is already being used.

      I've done many different tests, but none of them worked, and at the moment I'm clueless.

      I'd really appreciate any help, if someone has gone through this before.

      Thank you
      alessandro

        • 1. Re: 2 jboss instances clustered using same server
          Ben Wang Master

          Easiest way is to use multiple IP address binding, e.g.,

          run.sh -c node0 -b ${IP}

          -Ben

          • 2. Re: 2 jboss instances clustered using same server
            Alessandro Behling Newbie

            Hi Ben,

            Thank you for your help, I didn't know about that possibility. I'll keep in my deck.

            But, unfortunatelly I haven't got two IP addresses on my JBoss boxes, I've been having some progress, I'm testing a lot of different combinations of parameters, I know it sounds crazy, but it's the only way I've seen to try to understand how it works.

            At this point I'm getting this message:

            18:30:38,141 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
            MBeans waiting for other MBeans:
            ObjectName: jboss.j2ee:jndiName=clustering/HTTPSession,service=EJB
            state: NOTYETINSTALLED
            I Depend On: jboss:service=StagingPartition
            jboss:service=invoker,type=jrmp

            Depends On Me: jboss:service=ClusteredHttpSessionStaging

            everything else seems to be ok, no port conflicts, etc ...

            I'm sure I'm doing a terrible mistake, but I'm at that moment were I should have stopped hours ago ...

            Anyway, thanks in advance for any further help
            []s
            alessandro

            • 3. Re: 2 jboss instances clustered using same server
              Alessandro Behling Newbie

              Hi,

              I still have one problem, I changed the second JBoss instance confs in order to use a 'StagingPartition' has its partition name, there are no plances in any xml that has a reference to DefaultPartition, but during the startup this exception happens.

              Any idea? My JBoss version is 3.2.5

              Thank you
              alessandro

              13:00:34,934 ERROR [HASingletonController] Starting failed jboss.ha:service=HASi
              ngletonDeployerStaging
              javax.management.InstanceNotFoundException: Failed to find HAPartition with Part
              itionName=DefaultPartition
              at org.jboss.ha.jmx.HAServiceMBeanSupport.findHAPartitionWithName(HAServ
              iceMBeanSupport.java:388)
              at org.jboss.ha.jmx.HAServiceMBeanSupport.setupPartition(HAServiceMBeanS

              • 4. Re: 2 jboss instances clustered using same server
                Ben Wang Master

                HA-Singlton is using the DefaultPartition. Easiest way is to change the mcast address and port instead of partition name.

                -Ben