[
https://issues.apache.org/jira/browse/ARTEMIS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953690#comment-14953690
]
ASF GitHub Bot commented on ARTEMIS-252:
----------------------------------------
Github user clebertsuconic commented on the pull request:
https://github.com/apache/activemq-artemis/pull/193#issuecomment-147512861
@northlander I'll run some tests and will merge this shortly... I have
added the topic subscription case (which is actually a cool feature in top of
AMQ5) and I have done some improvements as your method was performing N^2 scan
(first scan and then doing scan over move(methodID)).
Look at my commit
https://github.com/clebertsuconic/activemq-artemis/commit/fd62c24904a7d9c32e8fd907273ba957dc609f63
> Retry message on DLQ - feature in JMX
> -------------------------------------
>
> Key: ARTEMIS-252
> URL: https://issues.apache.org/jira/browse/ARTEMIS-252
> Project: ActiveMQ Artemis
> Issue Type: Wish
> Components: Broker
> Affects Versions: 1.1.0
> Reporter: Petter Nordlander
> Priority: Trivial
> Fix For: 1.1.1
>
>
> A very useful feature in ActiveMQ (5) is the option to retry messages from
> DLQ to the queue the where originally sent to. This feature would be awesome
> in Artemis as well.
> This is exposed as JMX operations.
> retryMessages(selector/filter)
> retryMessage(messageId)
> According to Artemis docs, the original address/queue is already in messages
> put to DLQ, so a retry operation would be very similar to existing move to
> implement.
> The use case is simple - create a possibility to re-run all/some messages of
> a DLQ in one go, after some patch/fix/upgrade.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
