[
https://issues.apache.org/jira/browse/ARTEMIS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952462#comment-14952462
]
Petter Nordlander edited comment on ARTEMIS-252 at 10/11/15 10:14 PM:
----------------------------------------------------------------------
AMQ5 copy the message to all subscribers (i.e. back to the topic) with the
retry methods. So my PR should be backwards compatible with AMQ5. If that is a
good idea or not is another story. A retry only to failed subscribers would
probably be a better solution, but way more complex to implement and perhaps
not asked for a lot, I guess.
was (Author: northlander):
ActiveMQ (5) redeliver the message to all subscribers with the retry methods.
So it should be backwards compatible. If that is a good idea or not is another
story. A redelivery only to failed subscribers would probably be a better
solution, but way more complex to implement and perhaps not asked for a lot, I
guess.
> 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)
