You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Tim Bain <tb...@alumni.duke.edu> on 2015/11/01 15:44:34 UTC
Re: Messages erroneously rejected as duplicates
This sounds like a bug. Since Tim Bish (the only person I've seen support
ActiveMQ-CPP) didn't comment on it here, please submit a bug report in
JIRA, ideally with your consumer code (better: a stripped down minimal
version that produces the behavior without any irrelevant extras) to help
recreate the problem.
On Oct 28, 2015 3:13 AM, "spam trap" <no...@spamgourmet.com>
wrote:
> [ActiveMQ 5.11.2, ActiveMQ-CPP 3.9.0]
>
> A message consumer (using ActiveMQ-CPP) receives a message but does
> not send an acknowledgement (INDIVIDUAL_ACKNOWLEDGE mode) due an error
> elsewhere. The ActiveMQ consumer is closed and recreated later.
>
> The unacknowledged message is processed by the redelivery plugin in
> the server and after 2s being put into the same queue again (with
> redelivery=true).
>
> However the message is rejected as a duplicate and the following
> message is in the server log:
>
> 2015-10-27 16:37:43,023 | TRACE | ActiveMQ NIO Worker 633 | Queue |
> che.activemq.broker.region.Queue 1715 | 105 -
> org.apache.activemq.activemq-osgi - 5.11.1 | ack of
> ID:...-33658-1445944844467-3:4:619:1:1 with MessageAck {commandId =
> 20521, responseRequired = false, ackType = 1, consumerId =
> ID:...-45704-1445944819211-0:1:3:1, firstMessageId =
> ID:...-33658-1445944844467-3:4:619:1:1, lastMessageId =
> ID:...-33658-1445944844467-3:4:619:1:1, destination = queue://msgout,
> transactionId = null, messageCount = 1, poisonCause =
> javax.jms.JMSException: Suppressing duplicate delivery on connection,
> consumer ID:...-45704-1445944819211-0:1:3:1}
>
> Please advise.
>
>
Re: Messages erroneously rejected as duplicates
Posted by spam trap <no...@spamgourmet.com>.
On Sun, 1 Nov 2015 07:44:34 -0700, Tim Bain
<tb...@alumni.duke.edu> wrote:
>This sounds like a bug. Since Tim Bish (the only person I've seen support
>ActiveMQ-CPP) didn't comment on it here, please submit a bug report in
>JIRA, ideally with your consumer code (better: a stripped down minimal
>version that produces the behavior without any irrelevant extras) to help
>recreate the problem.
https://issues.apache.org/jira/browse/AMQCPP-586