activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6691) JMX - allow DLQ flag to be modified
Date Wed, 31 May 2017 11:40:04 GMT

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

ASF subversion and git services commented on AMQ-6691:
------------------------------------------------------

Commit d2c0eddaad7a5633d50c9a1fef2014b9fc0fb5bc in activemq's branch refs/heads/master from
[~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=d2c0edd ]

[AMQ-6691] allow dlq flag to be set via jmx to allow retry op after a restart - use destinations
element for long term persistence


> JMX - allow DLQ flag to be modified
> -----------------------------------
>
>                 Key: AMQ-6691
>                 URL: https://issues.apache.org/jira/browse/AMQ-6691
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: JMX
>    Affects Versions: 5.14.0
>            Reporter: Gary Tully
>             Fix For: 5.15.0
>
>
> AMQ-4483 introduces the destination flag but it is not persisted in the message store
and does not survive a restart.
> Adding the flag to the destinations element in the broker xml works around this however
it assumes prior knowledge.
> Allowing the flag to be set allows a retrospective change pending the next restart when
a modification to the destinations element can be picked up.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message