Entries in Failover Log File

2009-12-21 17:20:37,897, [TIBCO EMS Session Dispatcher (121)], DEBUG,   MqProcessInst.execActivityInLoop, - Retrying evaluation for event : 168003 with message : JMS-8401 [Session is closed] on action : SendProtocolMessage
2009-12-21 17:20:37,897, [TIBCO EMS Session Dispatcher (121)], DEBUG,   MqProcessInst.execActivityInLoop, - Error while executing activity (PublishToEAI,SendProtocolMessage) below. Sleep and Retry for the 0 th time
2009-12-21 17:20:58,335, [TIBCO EMS Session Dispatcher (121)], DEBUG,   MqProcessInst.execActivityInLoop, - Retrying evaluation for event : 168003 with message : JMS-8401 [Session is closed] on action : SendProtocolMessage
2009-12-21 17:20:58,335, [TIBCO EMS Session Dispatcher (121)], DEBUG,   MqProcessInst.execActivityInLoop, - Error while executing activity (PublishToEAI,SendProtocolMessage) below. Sleep and Retry for the 1 th time
2009-12-21 17:21:18,678, [TIBCO EMS Session Dispatcher (121)], DEBUG,   MqProcessInst.execActivityInLoop, - Retrying evaluation for event : 168003 with message : JMS-8401 [Session is closed] on action : SendProtocolMessage
2009-12-21 17:21:18,678, [TIBCO EMS Session Dispatcher (121)], DEBUG,   MqProcessInst.execActivityInLoop, - Error while executing activity (PublishToEAI,SendProtocolMessage) below. Sleep and Retry for the 2 th time
2009-12-21 17:21:38,960, [TIBCO EMS Session Dispatcher (121)], DEBUG,   MqProcessInst.execActivityInLoop, - Retrying evaluation for event : 168003 with message : JMS-8401 [Session is closed] on action : SendProtocolMessage
2009-12-21 17:21:38,960, [TIBCO EMS Session Dispatcher (121)], DEBUG,   MqProcessInst.execActivityInLoop, - Error while executing activity (PublishToEAI,SendProtocolMessage) below. Sleep and Retry for the 3 th time
2009-12-21 17:21:59,210, [TIBCO EMS Session Dispatcher (121)], DEBUG,   MqProcessInst.execActivityInLoop, - Retrying evaluation for event : 168003 with message : JMS-8401 [Session is closed] on action : SendProtocolMessage
2009-12-21 17:21:59,210, [TIBCO EMS Session Dispatcher (121)], DEBUG,   MqProcessInst.execActivityInLoop, - Error while executing activity (PublishToEAI,SendProtocolMessage) below. Sleep and Retry for the 4 th time
2009-12-21 17:22:19,506, [TIBCO EMS Session Dispatcher (121)], DEBUG,   MqProcessInst.execActivityInLoop, - Retrying evaluation for event : 168003 with message : JMS-8401 [Session is closed] on action : SendProtocolMessage
2009-12-21 17:22:19,506, [TIBCO EMS Session Dispatcher (121)], DEBUG,   MqProcessInst.execActivityInLoop, - Error while executing activity (PublishToEAI,SendProtocolMessage) below. Sleep and Retry for the 5 th time
2009-12-21 17:22:39,506, [TIBCO EMS Session Dispatcher (121)], ERROR,   MqProcessInst.execActivityInLoop, - Retry count(5) exhausted for event id:168003 Activity failed : PublishToEAI - Workflow is set to error or no longer processed 

The failover log can be configured through Logging->Failover Log in each cluster member category in the Configurator. It has the same parameters as all the other logging categories, but very few entries so that the file can be watched and easily understood.

Failover Limitations

All activities support failover and re-execution after restart, with the following exceptions:

The activities that do not support failover are:

• ImportClassificationScheme Activity
• ReclassifyRecord (Reclassify) Activity
• PrepareForImportCatalog Activity

  Activities run in the async execution mode are not supported for failover. For a list of activities that can be run in async execution mode, refer Workflow Activities. One exception to this is the InitiateSubFlow activity which can be run in both sync and async execution mode and both modes are supported for failover.

  Multiple process selections will not have a fully functional failover mechanism. If failover is required, it is recommended that the workflow utilize subflows.