OK, so I want to make sure I understand this correctly. You have two brokers (or is that two failover pairs?): frontend-standard-01 and backend-broker-name-1. The brokers are not configured in a network of brokers, though you're using your Camel routes to move messages between them. You have some number of Camel routes running in a separate JVM (i.e. not within any ActiveMQ broker). Does each Camel route run in the same JVM, or are they each in their own JVM? When the broker is restarted or a failover occurs, the JVM containing the Camel routes remains up, and attempts to reconnect to the broker immediately and automatically, and somewhere in this reconnection logic the subscription name is being constructed incorrectly. Is that all accurate?
JB, do you know whether the subscription name gets formed by the broker or by the client? If the latter, it's possible that this is actually a Camel bug, but I don't know enough about where that's done to know whether this is on the ActiveMQ side or the Camel side. Tim On Mon, Nov 25, 2019 at 6:24 AM Jean-Baptiste Onofré <j...@nanthrax.net> wrote: > Hi, > > honestly, I don't understand the problem, and I'm not able to reproduce > with simple Camel routes (running in Karaf). > > Regards > JB > > On 25/11/2019 14:05, Ashish Vaishno wrote: > > Hello JB, > > > > I have not set offlineDurableSubscriberTaskSchedule or > > offlineDurableSubscriberTimeout explicitly in my activemq.xml file. > > > > Regards > > Ashish > > > > > > > > -- > > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html > > > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com >
