[
https://issues.apache.org/jira/browse/ARTEMIS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952357#comment-14952357
]
ASF GitHub Bot commented on ARTEMIS-252:
----------------------------------------
GitHub user northlander opened a pull request:
https://github.com/apache/activemq-artemis/pull/193
ARTEMIS-252 adding Retry methods on JMX interface
A short-cut to move messages from DLQ to original queue via JMX operations
retryMessage( messageId ) for a single message and retryMessages() for all
messages.
Operations added to both JMS queue MBean and Core queue MBean.
https://issues.apache.org/jira/browse/ARTEMIS-252
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/northlander/activemq-artemis master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/193.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #193
----
commit 67ee840aba0e17eacdb5d4a9330901db98aeec9c
Author: Petter Nordlander <[email protected]>
Date: 2015-10-10T14:58:04Z
ARTEMIS-252 added jmx operations to retry messages
commit 472945c5f5578608eee65ea0dcee9b21a4a2efa0
Author: Petter Nordlander <[email protected]>
Date: 2015-10-11T17:34:23Z
ARTEMIS-252 Added support to retry messages via JMX on JMS Queue interface
----
> 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)
