Configuration of Resource Failure Handling

The following table describes the properties used for handling resource failure:

Resource Failure Handling Configuration
Sl No. Name Default Value Used Location
1 com.tibco.fom.orch.jms.socket.connection.timeout (JMS Socket connection timeout in milliseconds) 500 milliseconds Timeout interval for the socket, which is used to check the availability of the EMS server on the defined port. $OM_HOME/roles/configurator/standalone/config/ConfigValues_OMS.xml
2 com.tibco.fom.orch.jms.jndiLookup.connection.timeout (JMS JDNI connection check timeout in milliseconds) 10,000 millisecondsA threshold interval for which the thread waits to get the connection factory during lookup as part of the EMS monitoring. $OM_HOME/roles/configurator/standalone/config/ConfigValues_OMS.xml
3 com.tibco.fom.orch.db.connection.timeout (DB connection check timeout in milliseconds) 10,000 millisecondsA threshold interval for which the thread waits to get the database status during lookup as part of the database monitoring. $OM_HOME/roles/configurator/standalone/config/ConfigValues_OMS.xml
4 Heart beats interval 7,000 millisecondsInterval between successive heartbeat to check the availability of the node. Columns of the DOMAIN table of the Order Management Server user.
5 FT Threshold interval 100,000 millisecondsInterval after which the cluster manager assumes that the node has failed if it does not receive the heartbeat from a failed node. Columns of the DOMAIN table of the Order Management Server user.
6 Manager activation interval 40,000 millisecondsInterval to check if the node can become a cluster manager and start performing the cluster manager activities. Columns of the DOMAIN table of the Order Management Server user.
7 Advisory message publishes interval 7,000 millisecondsInterval at which a heartbeat is sent using the available resources from the database or JMS. This heartbeat information is used to identify whether to treat a node as a failed node or not.
Note: Value for this property is referred from the heartbeat interval. If you change the heartbeat interval, the advisory message publish interval is also changed to the same value.
Columns of the DOMAIN table of the Order Management Server user.
8 com.tibco.fom.orch.cluster.channel.maxIdleTime (Max Idle time reset the channel Error in Milliseconds) 120,000 milliseconds Interval used to reset the heartbeat channel error.  
9 Handle Failed Node 1 If the value is
  • 1: Cluster manager detects and recovers failed node event
  • -1: To disable cluster failover recovery
Columns of the DOMAIN table of the Order Management Server user.