You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Cott Lang (JIRA)" <ji...@apache.org> on 2017/08/11 17:37:00 UTC

[jira] [Commented] (AMQ-6691) JMX - allow DLQ flag to be modified

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

Cott Lang commented on AMQ-6691:
--------------------------------

is it not possible to persist the the flag? This is an improvement, but still leads to a lot of headaches with auto-created per-destination DLQs. :(

> 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.4.14#64029)