4 Replies Latest reply on May 7, 2014 4:51 AM by wdfink

    HA Singleton not starting up in domain mode - EAP 6.2.0

    antlia

      Hi to all,

       

      I'm implementing an HA Singleton which must  be deployed on a single node of a cluster.

       

      Following this guide: https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6/html/Development_Guide/Implement_an_HA_Singleton.html

       

      It works if I start the server in standalone mode with standalone-full-ha as server configuration, but, if I run the server in domain mode, using the full-ha profile, the Singleton is not starting up, its state is always DOWN.

       

      Can anyone help me?

      I've tried to debug the code noticing that no one is calling the notify() method in the NotifyingServiceListener, in fact, substituting the controller.wait(5000) instruction, with a simple controller.wait(), causes JBoss to stuck during deployment.

        • 1. Re: HA Singleton not starting up in domain mode - EAP 6.2.0
          wdfink

          There is a quickstart cluster-ha-singleton which you might use for testing, it implement a simple timer singleton which should get fired on one node in the cluster.

           

          Using a domain should not have an effect to the cluster behaviour, except deployment, as each server process should work similar to a standalone instance.

          Do you see that the cluster is build correctly within the logfiles?

          • 2. Re: HA Singleton not starting up in domain mode - EAP 6.2.0
            antlia

            Hi Wolf,

            for debugging purposes I've started only one node of the cluster , the other are turned off, I've no exception in my logfiles.

            But even with only one node, the controller is not starting the service, its state is always DOWN, it never goes even in STARTING state.

             

            Also for me it's very strange that this behavior appears only in domain mode and not in standalone...but I've debugged in both modes, and with standalone I can see all the state transitions DOWN --> STARTING --> UP, in domain mode the state remains down.

             

            The only difference that I'm noting is this: using controller.wait() (so a blocking call, without timeout), in standalone mode the respective controller.notify() is called, in domain mode no. I've tried also substituting the notify() with the notifyAll() method, but it doesn't change anything.

            • 3. Re: HA Singleton not starting up in domain mode - EAP 6.2.0
              antlia

              Any suggest for this strange behavior?

              • 4. Re: HA Singleton not starting up in domain mode - EAP 6.2.0
                wdfink

                Did you test the cluster-ha-singleton with the ServiceActivator approach? This is the recommended approch if you use EAP6.2. You may dowload the quickstarts from the Red Hat portal.