Issue

Note, this article assumes the ActiveMQ broker runs standalone, not inside the Karaf container!! If the broker runs inside the Karaf container, this article does not apply.

Previous versions of ActiveMQ allowed to change users.properties and groups.properties while the broker remained running. These changes were loaded by the broker upon the next authentication request.

Starting with JBoss A-MQ 6.2.1, this is no longer the case. The broker does not seem to reload these property files.

The broker is configured for

<plugins>
  <jaasAuthenticationPlugin configuration="activemq" />
</plugins>

and login.config as

activemq {
    org.apache.activemq.jaas.PropertiesLoginModule required
        org.apache.activemq.jaas.properties.user="users.properties"
        org.apache.activemq.jaas.properties.group="groups.properties";
};