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. For this, the store needs a restart which is not practical. -- View this message in context: http://activemq.2283324.n4.nabble.com/Active-MQ-runtimeConfigurationPlugin-Set-Message-Priority-Not-working-tp4728264p4728590.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
