OIC Trigger Not Able To Receive Any Message From MQ Topic And Agent Logs Shows Error "com.ibm.msg.client.jms.DetailedInvalidClientIDException" (Doc ID 2883385.1)

Last updated on NOVEMBER 25, 2022

Applies to:

Symptoms

On : NA version, Jms Adapter

OIC not able to receive any message from MQ Trigger subscribed to topic and agent logs shows exception.

ERROR
-----------------------
[2022-07-13T18:35:31.167Z] [WARNING] [ThreadID: 43] [Logger: oracle.soa.adapter.jms.connection] [SRC Class: oracle.tip.adapter.jms.JMS.JMSConnection; Method: setClientID] JMSConnection_setClientID: not allowed to set ClientID com.ibm.msg.client.jms.DetailedInvalidClientIDException: JMSCC0111: IBM MQ classes for JMS attempted to set a pre-existing client ID on a Connection or JMSContext. An application attempted to set the client ID property of a valid Connection or JMSContext to the value 'ICS_210907033324924' but this value was already in use.
The clientId had already been set by Thread[Thread-9,5,]
Wed Jul 13 10:47:55 MDT 2022
: java.lang.Thread.getStackTrace(Unknown Source)
: com.ibm.msg.client.jms.internal.JmsConnectionImpl$ClientIDSetter.(JmsConnectionImpl.java:129)
: com.ibm.msg.client.jms.internal.JmsConnectionImpl.checkDuplicateClientID(JmsConnectionImpl.java:317)
: com.ibm.msg.client.jms.internal.JmsConnectionImpl.validateProperty(JmsConnectionImpl.java:1849)
: com.ibm.msg.client.jms.internal.JmsPropertyContextImpl.setObjectPropertyInternal(JmsPropertyContextImpl.java:450)
: com.ibm.msg.client.jms.internal.JmsPropertyContextImpl.setObjectProperty(JmsPropertyContextImpl.java:612)
: com.ibm.msg.client.jms.internal.JmsPropertyContextImpl.setStringProperty(JmsPropertyContextImpl.java:649)
: com.ibm.msg.client.jms.internal.JmsConnectionImpl.setClientID(JmsConnectionImpl.java:1030)
: com.ibm.mq.jms.MQConnection.setClientID(MQConnection.java:410)
: oracle.tip.adapter.jms.JMS.JMSConnection.setClientID(JMSConnection.java:459)
.......
. Ensure that the connection is valid and that the client ID is unique.
at sun.reflect.GeneratedConstructorAccessor84.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.ibm.msg.client.commonservices.j2se.NLSServices.createException(NLSServices.java:319)
at com.ibm.msg.client.commonservices.nls.NLSServices.createException(NLSServices.java:226)
at com.ibm.msg.client.jms.internal.JmsErrorUtils.createException(JmsErrorUtils.java:126)
at com.ibm.msg.client.jms.internal.JmsConnectionImpl.checkDuplicateClientID(JmsConnectionImpl.java:308)
at com.ibm.msg.client.jms.internal.JmsConnectionImpl.setClientID(JmsConnectionImpl.java:997)
at com.ibm.mq.jms.MQConnection.setClientID(MQConnection.java:410)
at oracle.tip.adapter.jms.JMS.JMSConnection.setClientID(JMSConnection.java:459)

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create a trigger for MQ Topic

 

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.