SAP Knowledge Base Article - Preview

2714749 - [JMSClientExceptions:055032]An attempt was made to create a named consumer on a connection with no clientID in JMS channel

Symptom

You are trying to connect to a WebLogic JMS server with a JMS channel with the transport protocol set to "Access JMS Provider with JNDI". When you try to start the channel you see the following error in the Communication Channel Monitor and in the default traces:

#Error#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#BC-XI-CON-AFW#com.sap.aii.af.lib#C0000A18103D052D000000000000091C#12519550000000004##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessionContext()#Guest#0##DCF696CB272D1006B0D0AAD134860C69#dcf696cb272d1006b0d0aad134860c69##0#Application [35]#Plain##
Unable to create new pooled resource: ConnectorException: Error creating message consumer: weblogic.jms.common.IllegalStateException: [JMSClientExceptions:055032]An attempt was made to create a named consumer (consumerNAME) on a connection with no clientID#

When you collect an XPI Inspector trace with Example 50 - XI Channel for the JMS channel you can see the following error:

[EXCEPTION]
weblogic.jms.common.IllegalStateException: [JMSClientExceptions:055032]An attempt was made to create a named consumer (consumerNAME) on a connection with no clientID
at weblogic.jms.client.JMSSession.throwWhenInvalidSubscriberName(JMSSession.java:2770)
at weblogic.jms.client.JMSSession.setupConsumer(JMSSession.java:2723)
at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:2691)
at weblogic.jms.client.JMSSession.createDurableSubscriber(JMSSession.java:2487)
at weblogic.jms.client.WLSessionImpl.createDurableSubscriber(WLSessionImpl.java:1233)
at com.sap.aii.adapter.jms.core.connector.SessionContextImpl.buildMessageConsumers(SessionContextImpl.java:286)
at com.sap.aii.adapter.jms.core.connector.SessionContextImpl.init(SessionContextImpl.java:85)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl$1.createNewResource(ConnectorImpl.java:172)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl$1.createNewResource(ConnectorImpl.java:163)
at com.sap.aii.af.lib.util.concurrent.AbstractResourcePool.getResource(AbstractResourcePool.java:151)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessionContext(ConnectorImpl.java:549)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doConnect(ConnectorImpl.java:434)
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doConnect(JndiConnectorImpl.java:198)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connectIfDisconnected(ConnectorImpl.java:250)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:233)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:423)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:180)
at com.sap.aii.adapter.jms.core.channel.AdapterImpl$1.run(AdapterImpl.java:987)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)


Read more...

Environment

  • SAP NetWeaver 7.1
  • SAP enhancement package 1 for SAP NetWeaver 7.1
  • SAP NetWeaver 7.3
  • SAP enhancement package 1 for SAP NetWeaver 7.3
  • SAP NetWeaver 7.4
  • SAP NetWeaver 7.5

Product

SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP NetWeaver Process Integration 7.1 ; SAP enhancement package 1 for SAP NetWeaver 7.3 ; SAP enhancement package 1 for SAP NetWeaver Process Integration 7.1

Keywords

Process Integration 7.31, PI 7.31, Process Orchestration 7.4, PI 7.4, PO 7.4, Process Orchestration 7.5, PI 7.5, PO 7.5, XI, AEX, setTopicConnectionClientID, WebLogic, JMS, JMSClientExceptions, weblogic.jms.common.IllegalStateException, com.sap.aii.adapter.jms.core.connector.ConnectorImpl , KBA , BC-XI-CON-JMS , JMS Adapter , BC-XI-CON-AFW , J2EE Adapter Framework , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.