activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <>
Subject Re: Camel Routing places KahaDB in an unexpected place
Date Mon, 18 Feb 2019 13:48:25 GMT
Thank you for all of those explanations. The first solution (increasing the
time between retries) didn't make sense to me, but your final explanation
fully explains the behavior. Thanks for sharing the information with the
list, to help anyone who hits this in the future.


On Wed, Feb 6, 2019, 3:14 PM bterhune < wrote:

> One last update.. The more I learn about what is going on, I realize the
> information I left out of my original post.
> The Camel configuration is connecting to the broker in question using the
> vm: protocol AND connecting to a remote broker.  The VM connection was the
> one causing reconnect to spin up an embedded instance of the broker using
> default configuration.
> The change I made was to not create a broker if is not running.
> <property name="brokerURL" value="failover:(vm://my-broker?create=false)"
> />
> --
> Sent from:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message