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-6091) Java runtime policy update should support a list of properties to apply retrospectively
Date Fri, 18 Dec 2015 18:22:46 GMT

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

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

Commit a12c21061ebc4cca9757d497f90ce00145c50968 in activemq's branch refs/heads/activemq-5.13.x
from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=a12c210 ]

https://issues.apache.org/jira/browse/AMQ-6091

The JavaRuntimeConfigurationBroker can now apply a subset of policy
properties retrospectively to existing destinations versus applying
all properties of the policy update.

(cherry picked from commit a253ad3c71a07bb4d1883fe84be217af9855cfc6)


> 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
>
> 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)

Mime
View raw message