JMSReceiver Not Setting The JMSExpiration And Other JMS Header Properties From The JMSSubsys Named Subsystem Parameter List (Doc ID 2338050.1)

Last updated on JANUARY 03, 2023

Applies to:

Symptoms

PRODUCT VERSIONS:
------------------------------

SIEBEL VERSION: Siebel 8.1.1.14.14 [IP2014]
SIEBEL APP O/S: Microsoft Windows x64 (64-bit)

ISSUE STATEMENT:
----------------------------

According to the following Siebel documentation, there are a list of JMS Header Properties which the Siebel JMSReceiver should be able to set on message:

https://docs.oracle.com/cd/E88140_01/books/EAI3/EAI3_EAIJMSTrans16.html#wp1092974

Siebel Bookshelf > Transports and Interfaces: Siebel Enterprise Application Integration > EAI JMS Transport > Configuring the EAI JMS Transport > About the JMSSubsys Named Subsystem

The arguments to any method of JMS Transport can be supplied individually as properties of the input property set or as part of a named 32-bit subsystem of type JMSSubsys. When invoking the JMS Transport asynchronously by starting a JMS Receiver component, the arguments must be supplied by way of a named subsystem.

This subsystem supplies all of the necessary parameters for any one of these three methods: ReceiveDispatch, ReceiveDispatchSend, or SubscribeDispatch. The parameters for the three methods are ConnectionFactory, ReceiveQueue, SendQueue, Topic, SubscriberIdentifier, ReceiveTimeout, JMSType, JMSPriority, JMSExpiration, and JMSDeliveryMode.

STEPS TO REPRODUCE:
---------------------------------

During actual testing on different Siebel versions, the following were observed:

1. Testing on IP16, the above JMS Headers are listed in the JMSSubsys Named Subsystem Parameter list, but none of them are set to any value on the message which the JMSReceiver posts to the queue.

Ie, though the JMS Header such as JMSExpiration is set on the corresponding JMSExpiration Named Subsystem parameter with a value of 300, the message posted by JMSReceiver does not actually set any value to the JMSExpiration header on the message, it remains empty/blank.

2. On IP17 releases, none of the above JMS Headers are listed in the JMSSubsys Named Subsystem Parameter list anymore.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.