activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Bain <tb...@alumni.duke.edu>
Subject Re: dlqDeliveryFailureCause java.lang.Throwable: duplicate from store for queue
Date Tue, 09 Jan 2018 13:46:39 GMT
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 you should use 5.11.3 if you're going to upgrade to the 5.11 minor
version instead of 5.12, 5.13, etc.). Gary also referenced some workarounds
if you don't want to upgrade.

Most of the people who have reported this problem were using a network of
brokers (usually with three nodes in a mesh). Can you please describe your
network topology and show us your configuration from activemq.xml?

Tim

On Jan 8, 2018 3:39 PM, "alainkr" <akreienbuhl@gmail.com> wrote:

> Hello,
>
> Using AMQ 5.10, what would cause a message land in the deadletter queue
> with
> the following cause :
>
>
> dlqDeliveryFailureCause java.lang.Throwable: duplicate from store for queue
> X
>
>
> Thanks
>
> Alain
>
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>

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