[
https://issues.apache.org/jira/browse/AMQ-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15194090#comment-15194090
]
Petter Nordlander commented on AMQ-5662:
----------------------------------------
One way or the other I ended up with a new PR that should be in sync with
master rather than a rebase. Anyway, it's pretty much the same content and I
closed the previous PR.
Feel free to merge or comment.
https://github.com/apache/activemq/pull/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
> Priority: Minor
> Labels: webconsole
>
> 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)
