You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Laetitia <la...@dbmsrl.com> on 2023/03/17 14:22:16 UTC

Copy of duplicate delivery message in DLQ

Hi,

After having a case of "stuck messages" (as indicated in https://activemq.apache.org/networks-of-brokers.html), I've configured our Activemq instances with replayWhenNoConsumers.
Everything is working fine, but lately I have found few messages in DLQ with specific message "java.lang.Throwable: Suppressing duplicate delivery on connection, consumer..." in field "dlqDeliveryFailureCause".
That is something I was expected for version of Activemq lower than 5.17.x due to the specification of sendDuplicateFromStoreToDLQ (see https://activemq.apache.org/per-destination-policies), but I'm using version 5.17.3.

So, my question is, have I misunderstood the impact of sendDuplicateFromStoreToDLQ for detected duplicate delivery message in the context of "replayWhenNoConsumers" ? is it correct to have a copy in DLQ ?

Thanks for your kind help,

Laetitia

Re: Copy of duplicate delivery message in DLQ

Posted by Laetitia <la...@dbmsrl.com>.
Hello Matt,

Thank you.

Laetitia

----- Original Message -----
From: "Matt Pavlovich" <ma...@gmail.com>
To: users@activemq.apache.org
Sent: Tuesday, March 21, 2023 3:33:58 AM
Subject: Re: Copy of duplicate delivery message in DLQ

Hello Laetitia-

The message in the log is from the ActiveMQConsumer suppressing a duplicate, not a duplicate-from-store scenario. ‘sendDuplicateFromStoreToDLQ’ would not apply to this situation.

Thanks,
Matt Pavlovich

> On Mar 17, 2023, at 9:22 AM, Laetitia <la...@dbmsrl.com> wrote:
> 
> Hi,
> 
> After having a case of "stuck messages" (as indicated in https://activemq.apache.org/networks-of-brokers.html), I've configured our Activemq instances with replayWhenNoConsumers.
> Everything is working fine, but lately I have found few messages in DLQ with specific message "java.lang.Throwable: Suppressing duplicate delivery on connection, consumer..." in field "dlqDeliveryFailureCause".
> That is something I was expected for version of Activemq lower than 5.17.x due to the specification of sendDuplicateFromStoreToDLQ (see https://activemq.apache.org/per-destination-policies), but I'm using version 5.17.3.
> 
> So, my question is, have I misunderstood the impact of sendDuplicateFromStoreToDLQ for detected duplicate delivery message in the context of "replayWhenNoConsumers" ? is it correct to have a copy in DLQ ?
> 
> Thanks for your kind help,
> 
> Laetitia
>

Re: Copy of duplicate delivery message in DLQ

Posted by Matt Pavlovich <ma...@gmail.com>.
Hello Laetitia-

The message in the log is from the ActiveMQConsumer suppressing a duplicate, not a duplicate-from-store scenario. ‘sendDuplicateFromStoreToDLQ’ would not apply to this situation.

Thanks,
Matt Pavlovich

> On Mar 17, 2023, at 9:22 AM, Laetitia <la...@dbmsrl.com> wrote:
> 
> Hi,
> 
> After having a case of "stuck messages" (as indicated in https://activemq.apache.org/networks-of-brokers.html), I've configured our Activemq instances with replayWhenNoConsumers.
> Everything is working fine, but lately I have found few messages in DLQ with specific message "java.lang.Throwable: Suppressing duplicate delivery on connection, consumer..." in field "dlqDeliveryFailureCause".
> That is something I was expected for version of Activemq lower than 5.17.x due to the specification of sendDuplicateFromStoreToDLQ (see https://activemq.apache.org/per-destination-policies), but I'm using version 5.17.3.
> 
> So, my question is, have I misunderstood the impact of sendDuplicateFromStoreToDLQ for detected duplicate delivery message in the context of "replayWhenNoConsumers" ? is it correct to have a copy in DLQ ?
> 
> Thanks for your kind help,
> 
> Laetitia
>