EAI JMS Transport: Multiple JMS Subssystems

(Doc ID 529013.1)

Last updated on AUGUST 24, 2017

Applies to:

Siebel System Software - Version 7.8.2 SIA [19213] and later
Siebel CRM - Version 7.8.2 [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)


- 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 :-

9:39:47.719 AM Thu Feb 9: Invoking method SendReceive
9:39:47.719 AM Thu Feb 9: >ConnectionFactory=JMSConnFactory2
9:39:47.719 AM Thu Feb 9: >ConnectionUsername=
9:39:47.719 AM Thu Feb 9: >ConnectionPassword=*
9:39:47.719 AM Thu Feb 9: >SendQueue=MY.REQUEST
9:39:47.719 AM Thu Feb 9: >SendUsername=
9:39:47.719 AM Thu Feb 9: >SendPassword=*
9:39:47.719 AM Thu Feb 9: >ReceiveQueue=MY.REPLY
9:39:47.719 AM Thu Feb 9: >ReceiveUsername=
9:39:47.719 AM Thu Feb 9: >ReceivePassword=*
9:39:47.719 AM Thu Feb 9: >TopicUsername=
9:39:47.719 AM Thu Feb 9: >TopicPassword=*
9:39:47.719 AM Thu Feb 9: No cached connection found
9:39:47.812 AM Thu Feb 9: SendReceive failed.
9:39:47.812 AM Thu Feb 9: Error invoking SendReceive --

SiebelJMSException errorSubtype=LOOKING_UP_CONNECTION_FACTORY (wrapped exception = javax.naming.NameNotFoundException: JMSConnFactory2)
at com.siebel.eai.jms.b.a(SiebelJNDIContext.java)
at com.siebel.eai.jms.b.getFactory(SiebelJNDIContext.java)
at com.siebel.eai.jms.JMSBusinessService.a(JMSBusinessService.java)



JNDI error in EAI JMS Transport: 'Exception: javax.naming.NameNotFoundException: JMSConnFactory2; Message: JMSConnFactory2'.(SBL-EAI-05102) (0x8319)
[3] Object manager error: ([1] JNDI error in EAI JMS Transport: 'Exception: javax.naming.NameNotFoundException: JMSConnFactory2; Message: JMSConnFactory2'.(SBL-EAI-05102) (0x8319))

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms