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?
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.
Any suggest for this strange behavior?
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.