Siebel JMS Receiver Not Connecting To TIBCO Topic With Error "com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory cannot be cast to javax.jms.QueueConnectionFactory"

(Doc ID 2374788.1)

Last updated on MARCH 16, 2018

Applies to:

Siebel Universal Customer Master - Version 15.0 [IP2015] and later
Information in this document applies to any platform.

Symptoms

PRODUCT VERSIONS:
------------------------------
SIEBEL VERSION: Siebel 15.0 [IP2015]
SIEBEL APP O/S: Linux x86

ISSUE STATEMENT:
----------------------------
Topics have been created on Tibco application and Siebel named subsystems have been created to connect to the Tibco application Topics. When starting a task for a custom Siebel ChubTopicMTJMS server component to read from the JMS Topic, an error occurs.

ERROR MESSAGE:
--------------------------
The error message that occurs with this issue is:

ObjMgrBusServiceLog Error 1 00000aca5a9e1078:0 2018-03-06 12:22:10 (jmsbsvc.cpp (375)) SBL-EAI-05103: A JMS exception occurred in EAI JMS Transport: 'An unexpected error occurred (see StackTrace): com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory cannot be cast to javax.jms.QueueConnectionFactory'.

WHERE IT HAPPENED:
-------------------------------
The issue happens in all environments.

STEPS TO REPRODUCE:
---------------------------------
The behaviour occurs as follows:

1. Install Tibco version 5.11.0, build V57_hotfix14.

2. Create Topics on the Tibco application following the Tibco vendor software set up/instructions.

3. Create Siebel named subsystems for:

Receiver Data Handling Subsystem : ChubTopicJMSData
Receiver Connection Subsystem : ChubTopicSubSys

4. For these subsystems, specify the Tibco Topic and connection details.

5. Create a custom JMS Receiver component named ChubTopicMTJMS on the Siebel application that uses the above 2 subsystems for connection to Tibco.

6. Start a task for this custom ChubTopicMTJMS component, the task runs but fails to connect to Tibco with the reported error.

LOSS OF FUNCTIONALITY / BUSINESS IMPACT:
--------------------------------------------
Due to the error, Siebel application is not able to connect to the JMS Server to retrieve messages and process it.

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