Support Article
Unable to Browse messages in the JMS Listener
SA-49895
Summary
User's app is trying to connect to a secured JMS queue against Tibco.
The test connectivity is good but unable to browse messages or Put messages in the queue.
Behind the scenes, the user ID that is being passed to the queue is going in as "anonymous". User sees the following error in logs.
Error Messages
15:33:25,920 [ WebContainer : 5] [TABTHREAD0] [ ] [ APP:01.01.02] (ssages.Rule_Connect_JMS.Action) ERROR <ip1>|<ip2> APP_Test - Couldn't create connection object : javax.jms.JMSSecurityException: authentication failed
javax.jms.JMSSecurityException: authentication failed
at com.tibco.tibjms.Tibjmsx.buildException(Tibjmsx.java:543)
at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:1044)
at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:2707)
at com.tibco.tibjms.TibjmsQueueConnection.<init>(TibjmsQueueConnection.java:36)
at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:159)
at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:239)
Steps to Reproduce
Click Browse messages from JMS MDB Listener.
Root Cause
After diagnosing the issue by enabling trace level debugging in WebSphere, it was seen that Pega was passing what was needed.
Also, WebSphere had custom properties configured on the JNDI server such that "Username" and "Password" values were being added.
Resolution
Removed the "Username" and "Password" properties from application server configuration.
Note, that if these are required, they should be setup as "transport.jms.UserName" and "transport.jms.Password".
Published February 16, 2018 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.