Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
@Chandra Gorantla suggested to change the configuration for the authorizationEntry from queue to topic as the following:
<!-- Users in the minion role can read queue OpenNMS.Twin.Sink -->
<authorizationEntry topic="OpenNMS.Twin.Sink" read="minion" admin="minion" />
<!-- Users in the minion role can write queue OpenNMS.Twin.RPC -->
<authorizationEntry queue="OpenNMS.Twin.RPC" write="minion" admin="minion" />
After upgrading to Horizon 29.0.0 I have seen the following log entries on in the Karaf.log of the Minion:
12:22:09.904 WARN [Camel (camel-4) thread #9 - JmsConsumer[OpenNMS.Twin.Sink]] Setup of JMS message listener invoker failed for destination 'OpenNMS.Twin.Sink' - trying to recover. Cause: User minion is not authorized to read from: topic://OpenNMS.Twin.Sink
I've checked the opennms-activemq.xml configuration file and it has the following authorization entries:
<authorizationEntry queue="OpenNMS.Twin.Sink" read="minion" admin="minion" /> <authorizationEntry queue="OpenNMS.Twin.RPC" write="minion" admin="minion" />