Anil P. created AMQ-6772:
----------------------------
Summary: runtimeConfigurationPlugin - prioritizedMessages property
update at Runtime
Key: AMQ-6772
URL: https://issues.apache.org/jira/browse/AMQ-6772
Project: ActiveMQ
Issue Type: Bug
Components: runtime configuration plugin
Affects Versions: 5.14.5
Environment: Unix
Reporter: Anil P.
I have configured the 'runtimeConfigurationPlugin' and started the Active MQ.
Then added the below in policyEntries:
<policyEntry queue="test.configuration.dynamic.update"
prioritizedMessages="true" useCache="false" expireMessagesPeriod="0" />
After saving the config file, I am able to see that the console log got updated
saying that config changes are detected and loaded.
When tested, however, Message Priority is not being enforced as expected on the
queue.
I checked in JConsole, I am not able to update this particular property there
either.
If I restart with the policy configured, the property is getting applied and it
is working as expected. It is only not happening if I try to have it updated at
run-time.
Tim dug into the code, and discovered that the
PolicyEntry.update() and PolicyEntry.baseUpdate() methods (
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=blob;f=activemq-broker/src/main/java/org/apache/activemq/broker/region/policy/PolicyEntry.java;h=5b7ff0e184b9e6b4be6cf61ebcacc0a845bb1a6c;hb=HEAD)
don't attempt to set any of the three properties being passed in.
Please fix this so that those attributes will be set when the policy entry is
reloaded.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
