Re: Active MQ - runtimeConfigurationPlugin - Set Message Priority - Not working

This is what is updated in the JIRA (FYI) - this not going to be fixed, may be: the priority support is not a good candidate for runtime modification because not only do the in-memory messages need to retained in priority memory, the store needs to retrieve and store messages in priority order.

Re: Active MQ - runtimeConfigurationPlugin - Set Message Priority - Not working

Thanks Tim. Created https://issues.apache.org/jira/browse/AMQ-6772 -- View this message in context: http://activemq.2283324.n4.nabble.com/Active-MQ-runtimeConfigurationPlugin-Set-Message-Priority-Not-working-tp4728264p4728584.html Sent from the ActiveMQ - User mailing list archive at

Re: Active MQ - runtimeConfigurationPlugin - Set Message Priority - Not working

I finally got some time to dig into the code, and discovered that the PolicyEntry.update() and PolicyEntry.baseUpdate() methods (

Re: Active MQ - runtimeConfigurationPlugin - Set Message Priority - Not working

Sorry, Tim. I miss understood your previous question. 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 runtime. -- View this message in context:

Re: Active MQ - runtimeConfigurationPlugin - Set Message Priority - Not working

To make sure I'm understanding your answer: when you *restart* the broker, you see a log line saying that the broker applied your configuration, but it doesn't have the desired effect. Is that what you're saying? On Jul 14, 2017 5:07 AM, "akpuvvada" wrote: > No, Tim. > I

Re: Active MQ - runtimeConfigurationPlugin - Set Message Priority - Not working

No, Tim. I can see an update in the log that the configuration is updated, however the policy is not getting applied. When seen in JConsole, the detestation property is not showing as set. Thanks Anil -- View this message in context:

Re: Active MQ - runtimeConfigurationPlugin - Set Message Priority - Not working

Just to be sure: if you restart ActiveMQ with the policy in place, is it applied as expected? I want to make sure that the only thing not working is the application of the change at runtime. On Jul 13, 2017 3:35 AM, "akpuvvada" wrote: > Hi Tim, > > You are correct that the

Re: Active MQ - runtimeConfigurationPlugin - Set Message Priority - Not working

Hi Tim, You are correct that the property is not getting updated. Even in JConsole, I am not able to update this particular property. I guess this is not settable at Run-time. Any idea? -- View this message in context:

Re: Active MQ - runtimeConfigurationPlugin - Set Message Priority - Not working

Can you please confirm via JMX that the queue in question (with that exact name) has PrioritizedMessages=true in its attributes? Let's make sure the problem is that the setting isn't getting applied, rather than that it's getting applied but not having the expected result. Tim On Jul 6, 2017