EAI JMS Transport: Multiple JMS Subssystems
(Doc ID 529013.1)
Last updated on AUGUST 19, 2022
Applies to:
Siebel CRM - Version 7.8.2 [19213] and laterSiebel System Software - Version 7.8.2 SIA [19213] and later
Information in this document applies to any platform.
Symptoms
SBL-EAI-05102
Requirement is to call EAI JMS Transport, and implement a fail-over strategy for doing "SendReceives" to JMS queues.
Here is the setup:
- Two JMS Subsystems defined on the Siebel Server: JMSSubSys1, JMSSubSys2
- Two JAVA subsystems defined: Java1, Java2
- Java1 has in its classpath a jndi.properties file that includes bindings for JMS Queue 1 (an MQ Queue Manager)
- Java2 has in its classpath a jndi.properties file that includes bindings for JMS Queue 2 (an MQ Queue Manager)
NOTE: Having extra trailing spaces, extra newlines, CR/LF, square brackets, square characters, non-printable characters in the jndi.properties file can lead to errors.
Please review the jndi.properties file's content to ensure there are no non-printable characters such as trailing spaces, extra newlines, CR/LF, square brackets, etc.
Use a text editor which can display/identify binary characters, non-printable characters in the jndi.properties file and remove these from the file.
- JMSSubSys1 uses Java1
- JMSSubSys2 uses Java2
A Workflow Process attempts to send a JMS Message using "Send/Receive" through JMSSubSys1. If this "Send/Receive" fails, then, on the error branch, an attempt is made to send the message again, but this time using JMSSubSys2.
However, the following messages are reported :-
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 |