Administrator 5.1.3: Service Instance Status shows "Starting Up"
book
Article ID: KB0086344
calendar_today
Updated On:
Products
Versions
TIBCO Administrator
-
Not Applicable
-
Description
Description: Symptoms ======== Service Instance Status shows "Starting Up" even if the Service Instance has already been started successfully.
Impact ====== Loss of functionality
Cause ===== This case is applicable if Administrator is using non-default RV parameters for HAWK Agent.
1. ami_rvd_session parameter is added in Admin 513 which is used for local HMA communication. In the case of 512 to 513 upgrade, since the hawkagent.cfg file is not touched, the Service Instance TRA will use default 7474 for this value thus you are seeing HMA created on 7474 port and service instance status as "Starting Up". The newly deployed components will use this ami_rvd_session for deployed Hawk session parameters in its *.tra file. 2. rvd_session is used for possible remote connection scenario (in case of spanning subnets)
a) Note down value of -rvd_session (e.g. -rvd_session 8441 ; tcp:8441) i.e service = 8441 network = ; daemon = tcp:8441 b) Uncomment -M AMIService c) Uncomment -ami_rvd_session ; append service = service value for rvd_session + 1, network = network value for rvd_session, daemon = daemon value for rvd_session (for example, the values after change will be: -ami_rvd_session 8442 ; tcp:8441) d) copy line in c) and paste it between -rvd_session and -tsm_traceLogFile under -M com.tibco.tra.tsm.TSM
2. Restart the hawkagent_<domain>
3. Undeploy the newly deployed Applications and then redeploy
Resolution ==========
It will be addressed in the next Administrator 5.1.3 hotfix.
Symptoms:
Cause:
Issue/Introduction
Administrator 5.1.3: Service Instance Status shows "Starting Up"
Attachments
Administrator 5.1.3: Service Instance Status shows "Starting Up"
get_app