okay thanks !
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
On Jan 12, 2018 7:55 AM, "alainkr" wrote:
Hello Tim,
Thanks for your reply.
I saw that post but it mentions the following issues that don't apply to our
setting:
- AMQ-4485 fixed in 5.9
I interpreted Gary to mean that this was the cause of, not the fix for, the
problem. But I could have misu
Hello Tim,
Thanks for your reply.
I saw that post but it mentions the following issues that don't apply to our
setting:
- AMQ-4485 fixed in 5.9
- AMQ-5266 jdbc store which we don't use
We're using 5.10.0 :
- with no network of brokers.
- basic queue's and topics
We're planing to use authentica
Gary's response in
http://activemq.2283324.n4.nabble.com/dlqDeliveryFailureCause-java-lang-Throwable-duplicate-from-store-for-queue-td4691288.html
suggests upgrading to 5.11.0 or later (later is better, and at a minimum
you should upgrade to the last incidental version within a minor version,
so yo
those warnings and the moving of message to the DLQ in 5.9 reflect
changes in the broker core that attempt to address duplicate dispatch
and skipped dispatch of messages when the cache and the message store
get out of sync.
In the main it can be avoided by disabling the cache but the best
approach
