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

Petter Nordlander commented on ARTEMIS-252:
-------------------------------------------

In ActiveMQ it's defined only on the QueueViewMBean - so it's not something for 
topics.

QViewMBean.java:

    @MBeanInfo("Moves a message with the given JMS message back to its original 
destination")
    boolean retryMessage(@MBeanInfo("messageId") String messageId) throws 
Exception;
    
   @MBeanInfo("Retries messages sent to the DLQ")
    public int retryMessages() throws Exception;

It's used, for instance, in the Hawt.io ActiveMQ plugin (there is a "Retry" 
button beside the "Move" button) as well through JMX calls. It's really 
convenient to use retry if you have 10+ messages with different destinations on 
a DLQ that you want to resend.

I can fix a pull request if you guys feel this is a good feature to bring from 
AMQ5 to Artemis. It's really just another JMX method or two.

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

Reply via email to