Wrong Instance status (not running) when re-deploy the application with a new clustername in new deployed CDD file
Article ID: KB0083803
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | 5.3/5.4 |
Description
Incorrect instance status (not running) is shown in TEA when redeploying the application after changing the clustername in the CDD file. This happens if you have not stopped the instances before redeploying with a new cluster name. Also, the new deployed application will not start due to a JMX port conflict.
This is an expected behavior. The BE-TEAgent checks the cluster name before returning the status of the instance.
This is an expected behavior. The BE-TEAgent checks the cluster name before returning the status of the instance.
Issue/Introduction
Wrong Instance status (not running) when redeploying the application with a new clustername in new deployed CDD file.
Environment
All Operating Systems
Resolution
The cluster name of the running agent must match the one of the deployed CDD file to return the correct status of the Instance. When you plan to change the cluster name in the CDD file, it is required to stop all instances before redeploying the application.
Additional Information
BETeagent
Feedback
Yes
No
Powered by
