Question

4
Replies
304
Views
MattE957 Member since 2017 12 posts
Welltok
Posted: 2 years ago
Last activity: 1 year 11 months ago
Closed
Solved

Pega JMS connection to RabbitMQ

Hello,

Setup:

Pega 7.2.2 with Tomcat running on Ubuntu 14.04

I see the following error in PegaRULES-2018-Mar-19.log :

2018-03-19 18:10:12,486 [ JMS-Thread-42] [ STANDARD] [ ] [ ] ( services.jms.JMSListener) ERROR .UserRevoked - Caught JMSException in listener UserRevoked
com.rabbitmq.jms.util.RMQJMSSecurityException: ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.
at com.rabbitmq.jms.admin.RMQConnectionFactory.instantiateNodeConnection(RMQConnectionFactory.java:149)
at com.rabbitmq.jms.admin.RMQConnectionFactory.createConnection(RMQConnectionFactory.java:103)
at com.rabbitmq.jms.admin.RMQConnectionFactory.createConnection(RMQConnectionFactory.java:84)
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.initializeConnection(JMSListener.java:1054)
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.runPoller(JMSListener.java:757)
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.run_(JMSListener.java:752)
at com.pega.pegarules.integration.engine.internal.services.listener.ServiceListenerBaseImpl.run(ServiceListenerBaseImpl.java:454)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.rabbitmq.client.AuthenticationFailureException: ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.
at com.rabbitmq.client.impl.AMQConnection.start(AMQConnection.java:342)
at com.rabbitmq.client.impl.recovery.RecoveryAwareAMQConnectionFactory.newConnection(RecoveryAwareAMQConnectionFactory.java:62)
at com.rabbitmq.client.impl.recovery.AutorecoveringConnection.init(AutorecoveringConnection.java:99)
at com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:900)
at com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:859)
at com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:817)
at com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:954)
at com.rabbitmq.jms.admin.RMQConnectionFactory.instantiateNodeConnection(RMQConnectionFactory.java:140)

However I can see successful logins in the RMQ log file when I restart Tomcat on the Pega application server:

2018-03-19 18:10:10.453 [info] <0.11481.154> connection <0.11481.154> (xx.xxx.xxx.xx:10372 -> xx.xxx.xxx.xxx:5672): user 'pega-events' authenticated and granted access to vhost 'pipeline_events'
any ideas how to troubleshoot this? I have javax.jms.ConnectionFactory and javax.jms.Queue entries in Tomcat context.xml that are working in other Pega env's. Seems like Pega might be overriding them?
Thanks!
***Updated by moderator: Lochan to add Categories***
***Updated by Moderator Marissa to add SR Details***
Data Integration System Administration SR Created
Moderation Team has archived post
Share this page LinkedIn