We've successfully customised and run the  External MQ Client example on a broker group defined within a Fabric.

We'd like to do the same with an external Camel application now.

We believe our demo is set up equivalently to the External MQ Client, however on running we receive the following errors:

mel-2) thread #3 - timer://foo Pipeline                       DEBUG Message exchange has failed: so breaking out of pipeline for exchange: Exchange[Message: Hello world.] Exception: org.springframework.jms.UncategorizedJmsException: Uncategorized exception occured during JMS processing; nested exception is javax.jms.JMSException: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not create Transport. Reason: java.io.IOException: Could not create discovery agent: fabric:cameltest

mel-2) thread #3 - timer://foo TimerConsumer                  WARN  Error processing exchange. Exchange[Message: Hello world.]. Caused by: org.springframework.jms.UncategorizedJmsException - Uncategorized exception occured during JMS processing; nested exception is javax.jms.JMSException: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not create Transport. Reason: java.io.IOException: Could not create discovery agent: fabric:cameltest

org.springframework.jms.UncategorizedJmsException: Uncategorized exception occured during JMS processing; nested exception is javax.jms.JMSException: Error while attempting to add new Connection to the pool; nested exception is javax.jms.JMSException: Could not create Transport. Reason: java.io.IOException: Could not create discovery agent: fabric:cameltest

Here are the project files in gists:

FloodTest

pom.xml

The POM has repository info removed for privacy.

Note that the zookeeper.url and zookeeper.password properties are configured. Their values are known to be correct, since they are the same for our customised External MQ Client demo and that works on the same brokers without complaint.

The same is true for the broker.username and broker.password properties.

We would be grateful if you could advise what's causing this exception.