Resolution:
Description:
============
JMSCorrelationID of queue Requestor in TIBCO Businessworks does not work well when using the static destination.

Environment:
===========
Version: all        
Hardware: all      
OS: all

Symptoms:
========
“JMS Queue Requestor” activity uses temporary destinations to ensure that reply messages are received only by the process that sent the request. It will not work well when using the static destinations

Resolution:
==========
The JMSCorrelationID was used to link the response message with the request message. If you did not set this value, the response message’s JMSCorrelationID should be the same as request messageID . Note that the EMS server will not actively check JMSCorrelationID for request/reply, even if the JMSCorrelationID is different. The requestor will receive any reply on that destination.

- “JMSCorrelationID” is used to link a response message with its related request message. For this you need to use the message selector for the correlation ID set while sending the request message if you want set correlation ID.

- “JMS Queue Requestor” activity uses temporary destinations to ensure that reply messages are received only by the process that sent the request. It will not work when using static destinations as there is no facility to provide the message selector, which is needed for correlation ID.

- In this case you can use a combination of “JMS Queue Sender” and “Get JMS Queue Message” in Request and “JMS Queue Receiver” and “Reply to JMS Message” activities to use a correlation id along with message selector. (Refer to the attached project. Filename: JMSCorrelationID.zip).

JMSCorrelationID of queue Requestor in TIBCO Businessworks does not work well when using the static destination.