[
https://issues.apache.org/jira/browse/AMQ-6091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher L. Shannon resolved AMQ-6091.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 5.14.0
5.13.1
All tests passed in CI.
> Java runtime policy update should support a list of properties to apply
> retrospectively
> ---------------------------------------------------------------------------------------
>
> Key: AMQ-6091
> URL: https://issues.apache.org/jira/browse/AMQ-6091
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.13.0
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Priority: Minor
> Fix For: 5.13.1, 5.14.0
>
>
> Right now when the {{JavaRuntimeConfigurationBroker}} is used to update a
> Policy entry, every property of the Policy is re-applied to matching
> destinations after update. It would also be nice if an optional list of
> properties could be provided during the update.
> The behavior of this option would be to still apply the entire Policy entry
> update (so all new destinations get the policy changes), but for existing
> destinations only properties that match what's in the property list would get
> applied.
> The use case here would be wanting to apply only one or more properties that
> changed on a Policy to a destination, but not wanting to overwrite the other
> properties that might have been changed since creation of the destination.
> For example, say through JMX someone updated the maxPageSize property on a
> specific Queue to something other than what is specified on the Policy.
> After the fact, it might be desirable to update a different property on the
> policy that matches that Queue and have it be applied to the Queue. Normally
> this policy update would overwrite all properties on the existing Queue, but
> in this case we would not want to overwrite the maxPageSize setting as it was
> changed after the fact. So providing a list of properties to apply would
> prevent that setting from being changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
