When twice deploying an application in FT with AppManage command only one service instance instead of two is seen in the Administrator GUI.
Article ID: KB0085834
Updated On:
| Products | Versions |
|---|---|
| TIBCO Runtime Agent (TRA) | - |
| Not Applicable | - |
Description
Resolution:
Description:
===========
When deploying a new application, the deploy action adds new service instances to the target machine. If both binding names are empty, the second instance can be added as expected and the default binding name is used.
In general, during the deploy action, If an application already exists the deploy action updates the existing application. It removes the existing instance and creates a new one with respect of the settings in the configuration file.
When deploying for the second time, the first instance is removed and replaced. When updating the second instance, it is removed but not recreated since the deploy action thinks it is the same as the first which has been already updated. This is why only one instance is seen that is created when deploying for the second time even if the configuration file is the same.
Resolution
= = = = = =
As a workaround, it is possible to set different binding names in the deployed configuration XML file or delete the application first before re-deploying it.
Description:
===========
When deploying a new application, the deploy action adds new service instances to the target machine. If both binding names are empty, the second instance can be added as expected and the default binding name is used.
In general, during the deploy action, If an application already exists the deploy action updates the existing application. It removes the existing instance and creates a new one with respect of the settings in the configuration file.
When deploying for the second time, the first instance is removed and replaced. When updating the second instance, it is removed but not recreated since the deploy action thinks it is the same as the first which has been already updated. This is why only one instance is seen that is created when deploying for the second time even if the configuration file is the same.
Resolution
= = = = = =
As a workaround, it is possible to set different binding names in the deployed configuration XML file or delete the application first before re-deploying it.
Issue/Introduction
When twice deploying an application in FT with AppManage command only one service instance instead of two is seen in the Administrator GUI.
Feedback
Yes
No
Powered by
