HornetQ backup server activity depends on starting order in dedicated topology
Issue
The backup HornetQ functionality is only available when the backup-server is started before the live server. Only then one sees the expected messages like backup announced. Our use case is as follows
1.: start live server
2.: start dedicated backup server
--> No backup announced
3.: start backup server
4.: start live server
--> backup server announced as expected
Our expectation is that servers must "find" each other no matter in which order they are started. We also expect that failover is working independetly of startup order.
Environment
- Red Hat JBoss Enterprise Application Platform (EAP) 6.4.7
- HornetQ with replicated store
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.