Siebel JMS Receiver Tasks Ended With Errors - SBL-EAI-05000 JMS_EXCEPTION And 'Exception: javax.jms.InvalidClientIDException: CWSIA0028E: The client Id %1 is invalid as a connection with the same client Id is already running'
(Doc ID 3026285.1)
Last updated on JUNE 06, 2024
Applies to:
Siebel CRM - Version 16.19 [IP2016] and laterInformation in this document applies to any platform.
Symptoms
On a Test / UAT environment, the JMS Receiver component is running in multi-threaded mode with these parameters:
- Minimum Number of Work Queue Threads (MinWorkQThreads) = 4
- Maximum Number of Work Queue Threads (MaxWorkQThreads) = 4
These would ensure starting a number of 1 parent + 3 child/subtask of JMSReceiver when that component is started.
However, after some time, only one of these would remain running, the others would stop with the error in JMSReceiver logs:
ObjMgrBusServiceLog Error 1 000000ea66174f80:0 2024-04-11 11:10:39 (javabsvc.cpp (448)) SBL-EAI-05000: Business Service call returned error code JMS_EXCEPTION and message: Exception: javax.jms.InvalidClientIDException: CWSIA0028E: The client Id siebel.uat is invalid as a connection with the same client Id is already running.; Message: CWSIA0028E: The client Id siebel.uat is invalid as a connection with the same client Id is already running.
ObjMgrBusServiceLog Error 1 000000ea66174f80:0 2024-04-11 11:10:39 (jmsbsvc.cpp (375)) SBL-EAI-05103: A JMS exception occurred in EAI JMS Transport: 'Exception: javax.jms.InvalidClientIDException: CWSIA0028E: The client Id siebel.uat is invalid as a connection with the same client Id is already running.; Message: CWSIA0028E: The client Id siebel.uat is invalid as a connection with the same client Id is already running.'.
EAIReceiver EAIReceiverInfo 3 000000ea66174f80:0 2024-04-11 11:10:39 Retry Attempt '10': Trying to connect to the server.
GenericLog GenericError 1 000000ea66174f80:0 2024-04-11 11:10:39 Object manager error: ([0] A JMS exception occurred in EAI JMS Transport: 'Exception: javax.jms.InvalidClientIDException: CWSIA0028E: The client Id siebel.uat is invalid as a connection with the same client Id is already running.; Message: CWSIA0028E: The client Id siebel.uat is invalid as a connection with the same client Id is already running.'.(SBL-EAI-05103) (0x2313ef))
...
GenericLog GenericError 1 000000ea66174f80:0 2024-04-11 11:10:39 ( (0) err=2818155 sys=2298863) SBL-OMS-00107: Object manager error: ([0] A JMS exception occurred in EAI JMS Transport: 'Exception: javax.jms.InvalidClientIDException: CWSIA0028E: The client Id siebel.uat is invalid as a connection with the same client Id is already running.; Message: CWSIA0028E: The client Id siebel.uat is invalid as a connection with the same client Id is already running.'.(SBL-EAI-05103) (0x2313ef))
GenericLog GenericError 1 000000ea66174f80:0 2024-04-11 11:10:39 (eaircvr.cpp (1665) err=2294713 sys=0) SBL-EAI-00953: Call of Service 'EAI JMS Transport', Method 'SubscribeDispatch' failed: 2298863
The steps to reproduce that were:
1. Start the JMS Received component;
2. Monitor its execution and tasks;
3. See the error details in logs.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |