Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Matt Ellison (MattE957)
Welltok

Welltok
US
MattE957 Member since 2017 12 posts
Welltok
Posted: Mar 19, 2018
Last activity: Oct 24, 2018
Posted: 19 Mar 2018 21:35 EDT
Last activity: 24 Oct 2018 21:33 EDT
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 :

Show More

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***

Show Less
To see attachments, please log in.
Data Integration
System Administration
Support Case Created

Accepted Solution

Posted: 6 years ago
Posted: 20 Mar 2018 13:53 EDT
Matt Ellison (MattE957)
Welltok

Welltok
US

Hello,

The resolution was to add the RMQ auth creds to Designer Studio --> Integration Resources --> JMS listener 

Under the JMS properties tab. I didn't think Pega need this info , since it was already defined in the Tomcat context.xml file. Seems like it needs to be stored within Pega, and also Tomcat.

-Matt

To see attachments, please log in.
Posted: 6 years ago
Posted: 20 Mar 2018 13:32 EDT
Marissa Rogers (MarissaRogers)
MOD
Principal Knowledge Management Specialist
Pegasystems Inc.
US

Hi Matt,

I have updated your post with the SR that you created. I have also updated the SR with this PSC post.

I just spoke with the Support Engineer working your SR and he says this should continue on the SR. Please let us know the resolution once complete.

Thank you!

To see attachments, please log in.

Accepted Solution

Posted: 6 years ago
Posted: 20 Mar 2018 13:53 EDT
Matt Ellison (MattE957)
Welltok

Welltok
US

Hello,

The resolution was to add the RMQ auth creds to Designer Studio --> Integration Resources --> JMS listener 

Under the JMS properties tab. I didn't think Pega need this info , since it was already defined in the Tomcat context.xml file. Seems like it needs to be stored within Pega, and also Tomcat.

-Matt

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice