TIBCO Administrator on Startup invokes two RVD process, though RVRD binaries are already configured on the default port (7500).

TIBCO Administrator on Startup invokes two RVD process, though RVRD binaries are already configured on the default port (7500).

book

Article ID: KB0086299

calendar_today

Updated On:

Products Versions
TIBCO Administrator -
Not Applicable -

Description

Resolution:
Description:
============

When Administrator starts, it spawns one extra RVD process, though RVRD had been configured to run on the default port. Also, only Administrator is running on this machine. But Administrator searches for two RVD/RVRD processes, one on port 7474 (TIBHawkDaemon port) and another on port 7500 (RV Daemon default port). 

Cause
====

TIBCO Administrator invokes or searches for two RVD/RVRD processes on port 7474 (TIBHawkDaemon) and port 7500( RV Daemon) on startup because TIBCO Administrator uses Hawk consoles internally on the default port 7474 and Hawk microagents on port 7500. In such cases, always one RVD process would start by default on 7474(TIBHawkDaemon) TCP port and another will start on 7500(RvDaemon) TCP port, Also, if you had configured only one RVRD (7500) , then by default  another RVD process would start on 7474 TCP port.

Resolution
=======

To avoid the spawning of another RVD on port 7474, the repo.hawkImplant attribute needs to be set to "False" in the TIBCO Administrator TRA file. There should always be two RVRDs configured to monitor RV traffic from the TIBCO Hawkagent and TIBCO Administrator. The reason behind this segregation is to avoid small Hawk packets from being stuck behind large data packets traffic for read and write activities caused by TIBCO Administrator.

Issue/Introduction

TIBCO Administrator on Startup invokes two RVD process, though RVRD binaries are already configured on the default port (7500).