My Oracle Support Banner

JMSExpiration header not included in data put on response queue by JMS Receiver. (Doc ID 737934.1)

Last updated on JANUARY 03, 2023

Applies to:

Siebel CRM - Version 7.8.2.3 SIA [19221] and later
Information in this document applies to any platform.
Information in this document applies to any platform.

Symptoms


A customer is using the JMS application IBM Websphere MQ 6.0.2.2 and running a JMS Receiver task with Receiver Method Name set to ReceiveDispatchSend. The parameter JMSExpiration has been set to 150000 on the JMSSubsys. A message is correctly put on the response queue but it appears that the JMS header JMSExpiration is not included in the data.

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


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