You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2017/05/31 11:44:04 UTC
[jira] [Resolved] (AMQ-6691) JMX - allow DLQ flag to be modified
[ https://issues.apache.org/jira/browse/AMQ-6691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Tully resolved AMQ-6691.
-----------------------------
Resolution: Fixed
Assignee: Gary Tully
Test that validates persistence of the dlq flag via the destinations element of the broker xml is at:
https://git1-us-west.apache.org/repos/asf?p=activemq.git;a=commit;h=18d05ba5e0a96d231a357eb0a20b1f6388cb6c49
> 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
> Assignee: 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)