| 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.
|
$AF_HOME/roles/configurator/standalone/config/ConfigValues_OMS.xml
|
| 2
|
com.tibco.fom.orch.jms.jndiLookup.connection.timeout (JMS JDNI connection check timeout in milliseconds)
|
10000 milliseconds
|
A threshold interval for which the thread waits to get the connection factory during lookup as part of the EMS monitoring.
|
$AF_HOME/roles/configurator/standalone/config/ConfigValues_OMS.xml
|
| 3
|
com.tibco.fom.orch.db.connection.timeout (DB connection check timeout in milliseconds)
|
10000 milliseconds
|
A threshold interval for which the thread waits to get the database status during lookup as part of the database monitoring.
|
$AF_HOME/roles/configurator/standalone/config/ConfigValues_OMS.xml
|
| 4
|
Heart beat interval
|
7000 milliseconds
|
Interval between successive heart beat to check the availability of the node.
|
Columns of the DOMAIN table of the OMS user.
|
| 5
|
FT Threshold interval
|
100000 milliseconds
|
Interval after which the cluster manager assumes that the node has failed if it does not receive the heartbeat from failed node.
|
Columns of the DOMAIN table of the OMS user.
|
| 6
|
Manager activation interval
|
40000 milliseconds
|
Interval to check if the node can become a cluster manager and start performing the cluster manager activities.
|
Columns of the DOMAIN table of the OMS user.
|
| 7
|
Advisory message publish interval
|
7000 milliseconds
|
Interval at which a heartbeat is sent using the available resources from 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 heart beat interval. If you change the heart beat interval, the advisory message publish interval will also be changed to same value.
|
Columns of the DOMAIN table of the OMS user.
|
| 8
|
com.tibco.fom.orch.cluster.channel.maxIdleTime (Max Idle time reset the channel Error in Milliseconds)
|
120000 milliseconds
|
Interval used to reset the heartbeat channel error.
|
|
| 9
|
Handle Failed Node
|
1
|
If the value is
- 1: Cluster manager will detect and recover failed node event
- -1: To disable cluster fail over recovery
|
Columns of the DOMAIN table of the OMS user.
|
