[
https://issues.apache.org/jira/browse/ARTEMIS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14951858#comment-14951858
]
clebert suconic commented on ARTEMIS-252:
-----------------------------------------
I like the idea yeah.
I just wanted to clarify what to do on the topic case. If you resend back to
the address all subscriptions will get the message. Do we need to send back to
the single subscription where it came from?
If u send a PR I can complete with the topic case if needed. There is hack that
could be used to limit a core internal queue or topic subscriptions
> 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
>
> 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)
