Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Unable to connect to Tibco JMS queues



Pega 7.3.1 is set up with JBoss Enterprise Application Platform (JBoss EAP) 7.1.0 GA.
Error occurs when connecting Java Message Service (JMS) listeners to the Tibco queues.

Error Messages

Caused by: Failed to intialize response connection properties(JMS Factory lookup step) at Caused by: javax.naming.AuthenticationException: Not permitted: authentication failed [Root exception is javax.jms.JMSSecurityException: authentication failed] at com.tibco.tibjms.naming.TibjmsContext.lookup( at com.tibco.tibjms.naming.TibjmsContext.lookup( at javax.naming.InitialContext.lookup( at javax.naming.InitialContext.lookup( at ... 172 more Caused by: javax.jms.JMSSecurityException: authentication failed at com.tibco.tibjms.Tibjmsx.buildException(

Steps to Reproduce


Root Cause

A defect or configuration issue in the operating environment.
Error occurs because authorization is enabled in Enterprise Management Service (EMS).


Add the below settings in the Custom Properties tab of Java Naming and Directory Interface (JNDI) server instance.


Published December 4, 2018 - Updated October 8, 2020

Was this useful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

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

Pega Community 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
Contact us