Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Mon, 12 Oct 2015 21:28:06 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: issues@activemq.apache.org
Message-ID: <JIRA.12903906.1444426781000.17274.1444685286528@Atlassian.JIRA>
In-Reply-To: <JIRA.12903906.1444426781000@Atlassian.JIRA>
References: <JIRA.12903906.1444426781000@Atlassian.JIRA>
 <JIRA.12903906.1444426781582@arcas>
Subject: [jira] [Commented] (ARTEMIS-252) Retry message on DLQ - feature in
 JMX
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ARTEMIS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953767#comment-14953767 ] 

ASF GitHub Bot commented on ARTEMIS-252:
----------------------------------------

Github user northlander commented on the pull request:

    https://github.com/apache/activemq-artemis/pull/193#issuecomment-147527079
  
    @clebertsuconic Great! Thanks a lot for the topic part as well. 
    
    I know it was a bit bad performing but I didn't really want to modify code outside of management package for this tiny feature.
    

> 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)