jbonofre opened a new issue, #1920: URL: https://github.com/apache/activemq/issues/1920
The `RuntimeConfigurationPlugin.start()`, the plugin begins monitoring and processing configuration changes without checking whether the broker is in slave mode. The `broker.start()` call in `doStartBroker()` happens when slave is still true (it's only set to false later in `startAllConnectors()`). While this is typically fine because the lock is already acquired, the monitoring task schedule by the plugin runs periodically and doesn't check slave status. More importantly, the RuntimeConfigurationPlugin doesn't gate its behavior on slave mode at all. RuntimeConfigurationPlugin should check if the broker is a slave before applying modifications, and the monitoring task should also be slave-aware. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information, visit: https://activemq.apache.org/contact
