Plan items remain stuck in EXECUTION status after EMS server failover
book
Article ID: KB0076082
calendar_today
Updated On:
Products
Versions
TIBCO Fulfillment Order Management
3.x, 4.x
Description
It may happen that orders remain stuck in EXECUTION status after EMS failover. The root cause could be the fact that "JMSDeliveryMode" EMS message header property is set to "NON-PERSITENT". Consequently, plan item execute reply messages are deleted after EMS fail over.
Issue/Introduction
This article is about a use case in which plan items remain stuck in EXECUTION after EMS server fail over. It deals with issue root cause, how to avoid the problem and unblock orders already impacted.
Resolution
To avoid this issue, set header property JMSDeliveryMode=PERSITENT in plan item execute reply messages. Example: === $Header: JMSMessageID=ID:EMS-SERVER.37295E31601B6CE:131 JMSTimestamp=mar. févr. 04 17:24:08 213 CET 2020 JMSDestination=Queue[tibco.aff.orchestrator.planItem.execute.reply] JMSDeliveryMode=PERSISTENT ===
Note that messages on the queues are by default persistent and can be recovered at a later point of time if the consumer is not available at the time of message publishing or after ems server is restarted or in case of failover. However this is valid only if JMSDeliveryMode=PERSISTENT.
To unblock orders already impacted by this issue, you can SUSPEND and then RESUME them via OMSUI or using "Perform Bulk Order Action" web service.
Additional Information
FOM Administration guide. FOM Web Services guide.
Attachments
Plan items remain stuck in EXECUTION status after EMS server failover
get_app
Plan items remain stuck in EXECUTION status after EMS server failover
get_app