You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2018/02/01 14:22:00 UTC

[jira] [Resolved] (ARTEMIS-1645) Diverted messages cannot be retried from DLQ

     [ https://issues.apache.org/jira/browse/ARTEMIS-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram resolved ARTEMIS-1645.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.5.0

> Diverted messages cannot be retried from DLQ
> --------------------------------------------
>
>                 Key: ARTEMIS-1645
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1645
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 2.4.0
>            Reporter: Niels Lippke
>            Assignee: Justin Bertram
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: QueueControlTest.java
>
>
> Given a topic _SOURCE_ and a divert which forwards a message _M_ to a queue 
>  _TARGET_. Consumer fails to process _M_ and _M_ is being send to DLQ. 
>    
>  If you now retry _M_ from DLQ it is not send to _TARGET_ but you'll get 
>  {{AMQ222196: Could not find binding ...}}
>  instead.
>  And even worse the message is lost afterwards (removed from DLQ)! 
>    
>  My suspecion is, that the message properties are not correct regarding 
>  {{_AMQ_ORIG_ADDRESS}} and {{_AMQ_ORIG_QUEUE.}} 
>  Is: {{_AMQ_ORIG_ADDRESS=<Address from SOURCE>, _AMQ_ORIG_QUEUE=TARGET}} 
>  Should be:  {{_AMQ_ORIG_ADDRESS=<Address FROM TARGET>, _AMQ_ORIG_QUEUE=TARGET}} 
>    
>  Attached you'll find a testcase "testRetryDivertedMessage" which 
>  demonstrates the problem.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)