Also, to be clear, I don't believe that KahaDB has anything to do with this problem. The issue appears to be that the client ID assigned to the subscription on reconnection doesn't match the previous connection's value, which is independent of the persistence store type.
Tim On Thu, Nov 21, 2019, 6:57 AM Tim Bain <tb...@alumni.duke.edu> wrote: > Could you please share that configuration? > > I didn't understand from your earlier message that you were creating your > subscriptions using Camel, which adds another technology, and another > potential source of bugs, into the mix. > > Are both of your consumers staying up while the broker is restarted? And > are they running in the same JVM? > > Tim > > On Thu, Nov 21, 2019, 6:26 AM Ashish Vaishno <vaishno....@gmail.com> > wrote: > >> Hello Tim, >> >> I am setting the clientid in the file integration.camel.routes.xml, so >> that >> on each restart my durable susbcriber is always recognized and unique. >> >> Regards >> Ashish >> >> >> >> -- >> Sent from: >> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >> >
