A TIBCO Administrator Primary server shows "Starting Up" whereas the secondary server says "Running" for a deployed TIBCO BusinessEvents 3.x application.

A TIBCO Administrator Primary server shows "Starting Up" whereas the secondary server says "Running" for a deployed TIBCO BusinessEvents 3.x application.

book

Article ID: KB0088565

calendar_today

Updated On:

Products Versions
TIBCO BusinessEvents Enterprise Edition -
Not Applicable -

Description

Resolution:
Description:
============
A TIBCO Administrator Primary server shows "Starting Up" whereas thesecondary server says "Running" for deployed TIBCO BusinessEvents 3.x application.

Environment:
==========

TIBCO BusinessEvents 3.0.1 (BE)
TIBCO Administrator


Symptoms:
=========
Administrator shows the Primary server status as "Starting Up" whereas the secondary server status as "Running".


Cause:
=====
This is because the fault tolerant property is missing from the primary and secondary engine TRA files.


Resolution:
==========
In each engine property file, provide a short unique name for the engine using the property be.ft.nodename. This name is used by the fault tolerance cluster only. The name must not be more than 30 characters long

References:
==========
For more explanation, refer to Table 22 of Chapter 15 "Configuring In Memory Object Management" in the BE User's guide.

Issue/Introduction

A TIBCO Administrator Primary server shows "Starting Up" whereas the secondary server says "Running" for a deployed TIBCO BusinessEvents 3.x application.