Why are both service instances of TIBCO ActiveMatrix BusinessWorks application in Standby state when they were configured to run in FT mode?

Why are both service instances of TIBCO ActiveMatrix BusinessWorks application in Standby state when they were configured to run in FT mode?

book

Article ID: KB0075358

calendar_today

Updated On:

Products

TIBCO Administrator

Description


This can be caused by any of the following:

1). Incorrect RVFT transport parameter configuration.
2). RVRD configuration.
3). Network problem preventing the exchange of heartbeat messages.
4). On Linux environment we have observed there might be BW Ghost process running in background which causes conflict.

Issue/Introduction

Why are both service instances of an application in Standby state when they were configured to run in FT mode?

Environment

Product: TIBCO Administrator Version:5.7.x,5.8.0,5.9.x,5.10.0

Resolution

Check whether there is already an instance of a BW engine running with the same FT name on one of the machines within your domain. To do this:

1)  Shutdown all running instances of  BW engines through the Administrator GUI and check whether there are any BW engines still running, using the task manager under Windows or the ps command under Unix.

2). Check the FT name in the instance's .tra files that are being used by the running BW engines. The parameter to check is:
        Engine.FT.GroupName

3). Check whether different BW applications have the same value for this parameter (it should only be the same for instances of applications that are in a fault tolerant group).

4) . BW fault tolerance engines are running in the same subnet or a different subnet. If they are running in a different subnet, then the RVRD needs to be configured so that two engine instances can exchange RVFT heartbeat messages, which are required for FT operation.
(*** If RVRD is needed, before configuring RVRD, please stop all tibco applications including bwengine, hawk agent, RVD etc as these processes can start RVD automatically. Then start RVRD before starting any other applications.)

5). Check if heartbeat messages are being received on the machine running the BW instances. This can be done by : 
(You need specify the RV transport parameters if non-default parameters are used. You can check Bus.Default.Daemon, Bus.Default.Network, Bus.Default.Service in the instance's .tra file.)
    tibrvlisten "_RVFT.ACTIVE_HB.<FT subject name>"

    The <FT subject name> is specified in instance's .tra file: Engine.FT.Subject=<subject>

    If there is no heartbeat messages, it indicates a network or RVFT configuration problem.

6). There have been cases where a BW engine may start running outside the control of the Administrator (for example, in older versions if the instance had been redeployed using the -nostop and -nostart options).

Additional Information

Ref :000017377