How does the EMS selector Originator work when member is down?

book

Article ID: KB0084173

calendar_today

Updated On:

Products	Versions
TIBCO Fulfillment Order Management	2.1.2,3.0.1

Description

Resolution:
When a member is down FOM is continuously creating and destroying consumers with that selector. This is only happening if the member that is not running is part of the orchestrator cluster. If we use in ems set server log_trace=+DEFAULT,+PRODCONS,+CONNECT then we will see in logs:

Created consumer (connid=4726, sessid=8600, consid=7300) on queue 'tibco.aff.orchestrator.planItem.execute.reply' with selector "originator='Member2'"

Destroyed consumer (connid=4726, sessid=8600, consid=7300) on queue 'tibco.aff.orchestrator.planItem.execute.reply'

Environment