JMS expiration in messages.
Article ID: KB0092453
Updated On:
| Products | Versions |
|---|---|
| TIBCO Fulfillment Order Management | - |
| Not Applicable | - |
Description
Resolution:
FOM EMS messages, do not use expiration time (apart topics, only exception, see $AF_HOME/ems/AF_CreateEMSChannel.txt).
Example: Orchestrator plan item executes response. Do not use any JMS expiration time to avoid losing messages. Otherwise, the whole purpose of reliable asynchronous messaging is defeated.
-Synchronous operation:
Example: TDS synchronous request.
Customer has to implement a retry mechanism. Customer has to set the timeout and JMS expiration with the same value. Because the timeout is set to the same time that a message will live in EMS, OMS will discard the message and will not reply to a client that is not listening. No InvalidDestinationException exceptions will occur.
FOM EMS messages, do not use expiration time (apart topics, only exception, see $AF_HOME/ems/AF_CreateEMSChannel.txt).
Messages sent by customer to FOM:
-Asynchronous operation:Example: Orchestrator plan item executes response. Do not use any JMS expiration time to avoid losing messages. Otherwise, the whole purpose of reliable asynchronous messaging is defeated.
-Synchronous operation:
Example: TDS synchronous request.
Customer has to implement a retry mechanism. Customer has to set the timeout and JMS expiration with the same value. Because the timeout is set to the same time that a message will live in EMS, OMS will discard the message and will not reply to a client that is not listening. No InvalidDestinationException exceptions will occur.
Issue/Introduction
JMS expiration in messages.
Feedback
Yes
No
Powered by
