You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Matt Pavlovich (Jira)" <ji...@apache.org> on 2021/10/07 21:41:00 UTC

[jira] [Updated] (AMQ-8399) Allow maxAuditDepth and maxProducersToAudit changes via RuntimeConfig

     [ https://issues.apache.org/jira/browse/AMQ-8399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Pavlovich updated AMQ-8399:
--------------------------------
    Description: 
maxAuditDepth and maxProducersToAudit changes are editable via JMX, but not via runtime config plugin.

This feature request is to update the runtime config plugin to allow the change via policyEntry update

{noformat}
        // TODO
        // We currently need an infinite audit because of the way that browser dispatch
        // is done.  We should refactor the browsers to better handle message dispatch so
        // we can remove this and perform a more efficient dispatch.
        sub.setMaxProducersToAudit(Integer.MAX_VALUE);
        sub.setMaxAuditDepth(Short.MAX_VALUE);

        // part solution - dispatching to browsers needs to be restricted
        sub.setMaxMessages(getMaxBrowsePageSize());
{noformat}

  was:
maxAuditDepth and maxProducersToAudit changes are editable via JMX, but not via runtime config plugin.

This feature request is to update the runtime config plugin to allow the change via policyEntry update


> Allow maxAuditDepth and maxProducersToAudit changes via RuntimeConfig
> ---------------------------------------------------------------------
>
>                 Key: AMQ-8399
>                 URL: https://issues.apache.org/jira/browse/AMQ-8399
>             Project: ActiveMQ
>          Issue Type: Task
>            Reporter: Matt Pavlovich
>            Priority: Major
>
> maxAuditDepth and maxProducersToAudit changes are editable via JMX, but not via runtime config plugin.
> This feature request is to update the runtime config plugin to allow the change via policyEntry update
> {noformat}
>         // TODO
>         // We currently need an infinite audit because of the way that browser dispatch
>         // is done.  We should refactor the browsers to better handle message dispatch so
>         // we can remove this and perform a more efficient dispatch.
>         sub.setMaxProducersToAudit(Integer.MAX_VALUE);
>         sub.setMaxAuditDepth(Short.MAX_VALUE);
>         // part solution - dispatching to browsers needs to be restricted
>         sub.setMaxMessages(getMaxBrowsePageSize());
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)