You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Andrea Marziali (JIRA)" <ji...@apache.org> on 2016/04/11 00:40:25 UTC
[jira] [Commented] (AMQ-5079) compositeQueue and
deadLetterStrategy: messages disappearing
[ https://issues.apache.org/jira/browse/AMQ-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234316#comment-15234316 ]
Andrea Marziali commented on AMQ-5079:
--------------------------------------
As per CompositeDestinationFilter behaviour, what do you find should be achieved by setting copyMessage="true" on the compositeQueue element.
In this way, each destination has its own copy of the messages that will be handled independently
> compositeQueue and deadLetterStrategy: messages disappearing
> ------------------------------------------------------------
>
> Key: AMQ-5079
> URL: https://issues.apache.org/jira/browse/AMQ-5079
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.9.0
> Reporter: Colin Freas
> Priority: Critical
>
> Using a {{compositeQueue}} and a {{deadLetterStrategy}} like this:
> {noformat}
> <policyEntry queue=">">
> <deadLetterStrategy>
> <individualDeadLetterStrategy queuePrefix="DLQ." useQueueForQueueMessages="true"/>
> </deadLetterStrategy>
> </policyEntry>
> <compositeQueue name="order.queue">
> <forwardTo>
> <queue physicalName="order.queue-1" />
> <queue physicalName="order.queue-2" />
> </forwardTo>
> </compositeQueue>
> {noformat}
> The behavior I expect is this:
> * A message is sent to {{order.queue}}.
> * {{order.queue}} forwards messages to {{order.queue-1}} and {{order.queue-2}}.
> * {{order.queue-1}} and {{order.queue-2}} fail to process the message.
> * {{order.queue-1}} forwards message to {{DLQ.order.queue-1}}
> * {{order.queue-2}} forwards message to {{DLQ.order.queue-2}}
> The behavior I see is this:
> * A message is sent to the {{order.queue}}.
> * {{order.queue}} forwards messages to {{order.queue-1}} and {{order.queue-2}}.
> * {{order.queue-1}} and {{order.queue-2}} fail to process the message.
> * {color:red}{{order.queue-1}} message disappears.{color}
> * {{order.queue-2}} forwards message to {{DLQ.order.queue-2}}
> The messages on {{order.queue-1}} and {{order.queue-2}} have the same message ID, and it seems like that's the issue. When manually placing otherwise identical messages, the expected behavior is seen.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)