[
https://issues.apache.org/jira/browse/AMQ-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195161#comment-15195161
]
ASF subversion and git services commented on AMQ-5662:
------------------------------------------------------
Commit 37557e5dcf838bab05851d6b46bbe10456473f3c in activemq's branch
refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=37557e5 ]
https://issues.apache.org/jira/browse/AMQ-5662
Patch applied with thanks to Petter Nordlander
This closes #176
> Improve web console retry to support all DLQ names
> --------------------------------------------------
>
> Key: AMQ-5662
> URL: https://issues.apache.org/jira/browse/AMQ-5662
> Project: ActiveMQ
> Issue Type: Improvement
> Components: webconsole
> Affects Versions: 5.10.2, 5.11.1
> Reporter: Petter Nordlander
> Assignee: Christopher L. Shannon
> Priority: Minor
> Labels: webconsole
> Fix For: 5.14.0
>
>
> In web console, there is a "retry" link on a message when the name of browsed
> queue starts with DLQ. or DLT. The retry action in the console moves the
> letter to a queue named the same as the dead letter queue but without DLQ. or
> DLT.
> ActiveMQ, however, allows to use any name on a DLQ by using dead letter
> strategies. A shared strategy is the default, and the original destination is
> encoded in each message. The current implementation in web console cannot
> handle the default DLQ strategy in ActiveMQ, which has one single DLQ named
> ActiveMQ.DLQ.
> The suggested fix is to not rely on "move" to do a retry, but to use the
> built in retry mechanism instead. The second part of the fix is to only show
> the retry link when dealing with a real DLQ. A boolean is available through
> JMX.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
