[
https://issues.apache.org/jira/browse/ARTEMIS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952517#comment-14952517
]
clebert suconic commented on ARTEMIS-252:
-----------------------------------------
There's a property called HQ_ROUTE_ID (or something like that) that we use for
cluster communication, where we specify the ID of a queue.
We use the same hack on importing partial subscriptions and on scale down.
We could use the same here...
the inconvenient part is that the ROUTE_ID is a byteArray, very internal
thing.. but it could be a hack used.
Maybe we could make prettier and still use it.
I will merge it tomorrow.
> 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)
