TIBCO Components (Admin, BW engines, etc..) hang during start up. Error, "Failure contacting hawkagent".

TIBCO Components (Admin, BW engines, etc..) hang during start up. Error, "Failure contacting hawkagent".

book

Article ID: KB0092643

calendar_today

Updated On:

Products Versions
TIBCO Administrator -
Not Applicable -

Description

Resolution:
Title:
TIBCO Components (Admin, BW engines, etc..) hang during start up.  Error, "Failure contacting hawkagent".


Resolution:
Issue:
--------
1). TIBCO Administrator was not starting.
2). bwengines and adapters were not able to start.
3). The deployment was failing with the error, "Failure contacting hawkagent".

Debugging steps:
---------------------
1). Rule out machine resource related issues by running the fpollowoing:
     a). dmesg to check th /var/adm/messages. (May require root access).
     b). iostat
     c). top
     d). prstat

2). If machine resources are adequate, check the RVD log for entries such as "Too many open files". This  indicates that the limit for the number of File Descriptors(FD) had been exceeded.


TIBCO Administrator, TIBCO BW, and TIBCO Adapters try to open client connections to RVD. As the limit of FD for RVD processes have been exceeded, RVD is not able to open new client connections and the processes are  being blocked and appear to be hanging. Each new TCP connection consumes a FD and this FD limit is set at the user profile level. The system administrator can increase this default limit for the "tibco" user, which is used to start TIBCO applications. The user level limit can be verified by running the "ulimit -a" command. 

In Solaris 10, resources (such as FD limits or memory allocation) can be increased for a running process using the plimit command. Example: To set the FD to 8192, use  "plimit -n 8192,8192 <PID>".

Issue/Introduction

TIBCO Components (Admin, BW engines, etc..) hang during start up. Error, "Failure contacting hawkagent".
Powered by Wolken Software