Yes, I think it's our bug, but we need to figure out where. I'm hoping that you can help narrow down the symptoms to make it easier to find and fix (which increases the odds of it getting fixed, and is therefore in your best interest).
Tim On Nov 7, 2017 7:29 PM, "jasons" <jason.sm...@au.abb.com> wrote: > I missed the word "our" in your response which I now take to mean ActiveMQ > potential mishandling. > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User- > f2341805.html >
