Resolution:
This error happens when the Administrator is not responding due as it might be busy. In order to avoid this, please do the following configuration changes.

1. Specify a value for "operationRetry" or a larger value for "discoveryTime" in your domain properties files. For setting this property, you can modify the "TIB_REPO_URL" value in AdministrationDomain.properties and AuthorizationDomain.properties files. Please go through "TIBCO Administrator Server Configuration Guide -> Chapter 5 Advanced Topics -> Server-based Repository Locator String" documentation.

For example, discoveryTime\=30:operationRetry\=10
The TIB_REPO_URL in AdministrationDomain.properties may look like below:
TIB_REPO_URL=tibcr@SYS_tibco511F\:daemon\=tcp\:7521\:service\=7500\:discoveryTime\=30:operationRetry\=10

These values should be changed on the machine where the problem application is deployed to.

2. You can add property java.property.tra_deploy_timeout or increase its value in the  $TIBCO_HOME/administrator/domain/<domainname>/bin/tibcoadmin_domainname.tra file.

3. Increase the "repo.serverHeartbeatInterval" value in tibcoadmin_domainname.tra file. Increasing it will reduce the chance of a busy period being interpreted as the server died.