Symptom
You are experiencing problems with PO JMS channels. You encountered the issue while connecting to JMS queues during the network upgrade.
You attempted to connect to these JMS queues using telnet from the PO Server but discovered that they were unreachable.
After the network upgrade was done, you retested the telnet connection and discovered that it was still operational.
The PO JMS channels, on the other hand, did not automatically restart normal operation; they continued to fail.
The PO JMS channels were finally able to connect to the JMS queues after restarting the PO application server. So you're looking for RCA for this problem.
And you discovered the following traces in the logs.
[EXCEPTION]
javax.naming.ServiceUnavailableException: Failed to query JNDI: Failed to connect to the server at tcp://xxxxxxxxxxx:7222 [Root exception is javax.jms.JMSException: Failed to connect to the server at tcp://xxxxxxxxxxxx ]
at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:671)
at com.tibco.tibjms.naming.TibjmsContext.lookup(TibjmsContext.java:491)
Caused by: javax.jms.JMSException: Failed to connect to the server at tcp://xxxxxxxxxxxx
at com.tibco.tibjms.TibjmsxLinkTcp._createSocket(TibjmsxLinkTcp.java:823)
at com.tibco.tibjms.TibjmsxLinkTcp.connect(TibjmsxLinkTcp.java:914)
at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:1354)
Read more...
Environment
- SAP Process Orchestration
- SAP Process Integration
Product
Keywords
javax.naming.ServiceUnavailableException, Failed to query JND, Failed to connect to the server, Root exception is javax.jms.JMSException, TIBCO, com.Tibco.tibjms.naming.TibjmsContext.lookup. , KBA , BC-XI-CON-JMS , JMS Adapter , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.