Siebel Is Not Able To Access, Fetch Nor Retrieve The JMSReplyTo Header Value From A JMS Message (Doc ID 1990299.1)

Last updated on DECEMBER 24, 2022

Applies to:

Symptoms

A 3rd party application puts a message onto a JMS Server Queue. The message contains a JMSReplyTo header with data populated into it having the ReplyToQ information on which queue to send the response back to.

When Siebel application's JMSReceiver picks up the JMS Message from the JMS Server Queue, the message has a value in the JMSReplyTo header, but Siebel application is not able to access nor retreive the value from this JMSReplyTo header. As a result, it is not possible to know which queue to send the response back to once the message is processed on the Siebel side.

Steps to reproduce:

1. Create a workflow process and add a process property called JMSReplyTo to match the JMSReplyTo header property:

Process Property:      SIEBEL_JMS:JMSReplyTo
Data Type:               String
In/Out:                    In/Out

2. Deliver the workflow process to the workspace.

3. Restart Siebel server.

4. Use the 3rd party JMS application to put a message into the JMS queue with a value for the JMSReplyTo = TEST

5. Start a Siebel JMSReceiver task as follows:

Notice that despite the JMSReplyTo process property is there in the workflow process with the same name JMSReplyTo as the header, but there is no value populated, which means Siebel is not doing anything with the JMSReplyTo message header, the JMSReplyTo header is ignored.
 

Changes

Cause

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