Client blocking forever in its call to ConnectionFactory.createConnection() when Fabric discovery is used and broker is not running.
Issue
An JMS client that connects to the broker using Fabric discovery url "discovery:(fabric:default)" blocks forever on its call to
ConnectionFactory.createConnection() if the broker is not running and hence not registered in the Fabric Registry.
How can the client be configured to throw an exception instead?
Environment
- Fuse MQ Enterprise 7.x
- JBoss A-MQ 6.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.