-
Sub-task
-
Resolution: Done
-
Minor
-
EAP 5.1.0 Post Release
-
-
Documented as Resolved Issue
-
ON_QA
Hi Clebert,
MDB with activation property HA=true does not work with EAP default profile. MDB is not started because it "hangs up" in ServerLocatorImpl when is waiting for information about cluster topology.
HornetQException[errorCode=3 message=Timed out waiting to receive cluster topology]
at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:657)
Documentation should contain information about this feature (I have not found it). Or is it possible to implement better detection mechanism?