TIBCO InConcert server does not fire RVCM triggers.
Article ID: KB0088492
Updated On:
| Products | Versions |
|---|---|
| TIBCO InConcert | - |
| Not Applicable | - |
Description
Resolution:
Description:
============
The debug log shows the Event Action Daemon (EAD) appears to be processing triggers: debug: processNextAction Time: 0.225 however, no triggers are received by the client who is listening on the correct address.
Environment:
==========
All UNIX
Symptoms:
=========
The ledger file in IC_HOME/ledgers is not getting updated even though the EAD appears to be sending triggers.
Cause:
=====
The installation files were copied from another host and were owned by a different user. All files were transferred to a different user on the new system but the ledger file was not getting updated.
Resolution:
=========
Delete any ledgers files in IC_HOME/ledgers otherwise the new RVCM triggers can not be sent. The ledger file will be recreated with the correct permissions of the new user when the InConcert server is restarted.
Description:
============
The debug log shows the Event Action Daemon (EAD) appears to be processing triggers: debug: processNextAction Time: 0.225 however, no triggers are received by the client who is listening on the correct address.
Environment:
==========
All UNIX
Symptoms:
=========
The ledger file in IC_HOME/ledgers is not getting updated even though the EAD appears to be sending triggers.
Cause:
=====
The installation files were copied from another host and were owned by a different user. All files were transferred to a different user on the new system but the ledger file was not getting updated.
Resolution:
=========
Delete any ledgers files in IC_HOME/ledgers otherwise the new RVCM triggers can not be sent. The ledger file will be recreated with the correct permissions of the new user when the InConcert server is restarted.
Issue/Introduction
TIBCO InConcert server does not fire RVCM triggers.
Feedback
Yes
No
Powered by
