"JMS error: "clientId already exists - while starting SAP adapter
Article ID: KB0084125
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for SAP Solutions | 7.x |
Description
While starting an adapter, the following error is reported.
----Error String----
Processing /tibco/private/adapter/Sales_R3AdapterConfiguration/SAPAdapter ...
com.tibco.sdk.MNestedException: "JMS error: "clientId already exists
at com.tibco.sdk.jms.MJmsSession.init(MJmsSession.java:334)
at com.tibco.sdk.jms.MJmsSession.<init>(MJmsSession.java:78)
---Error String-----
Cause: The error generally occurs when an EMS client ID is being used by two different EMS connections at the same time. The client ID associated with one EMS connection must be either unique or null.
Issue/Introduction
JMS error: "clientId already exists" - while starting SAP adapter
Environment
All
Resolution
To address the above error:
- Run the command "show connections" from your EMS Administrator.
- Check if the client ID mentioned in the project is being displayed on the EMS Admin console.
- If the client ID is already used (some cases where the adapter project is already deployed on another machine using the same EMS server) then make sure to use a different/unique client ID in order to make the application run on both machine.
- Check all JMS sessions configured in your project and ensure that no two JMS connection is using the same client ID value.
-The basic criteria for an EMS client ID is that it should be either unique or null.
Also, to make the adapter generate a unique client ID for all related JMS connections, leave the client ID field as null when configuring the JMS connection.The adapter will by default generate a unique client ID upon saving the project. The will help in keeping the client ID unique.
- Run the command "show connections" from your EMS Administrator.
- Check if the client ID mentioned in the project is being displayed on the EMS Admin console.
- If the client ID is already used (some cases where the adapter project is already deployed on another machine using the same EMS server) then make sure to use a different/unique client ID in order to make the application run on both machine.
- Check all JMS sessions configured in your project and ensure that no two JMS connection is using the same client ID value.
-The basic criteria for an EMS client ID is that it should be either unique or null.
Also, to make the adapter generate a unique client ID for all related JMS connections, leave the client ID field as null when configuring the JMS connection.The adapter will by default generate a unique client ID upon saving the project. The will help in keeping the client ID unique.
Feedback
Yes
No
Powered by
