Troubleshooting

If you encounter problems with installation, make sure that your system meets all prerequisites. Next, check the installer log file for potential problems.

 

The following section is an update to the topic Troubleshooting in the TIBCO ActiveMatrix Service Grid Installation and Configuration Guide.

In TIBCO ActiveMatrix setup when secure SystemHost and RemoteHosts (Host for which JMX port is secured) are successfully upgraded to TIBCO ActiveMatrix Service Grid 3.4.0, the Administrator UI does not show the updated version of Hosts correctly.

Problem
When the Hosts are secured, SystemNode is configured with TLSv1 which is the supported TLS in versions of TIBCO ActiveMatrix prior to 3.4.0. Starting TIBCO ActiveMatrix 3.4.0 TLSv1.2 is supported, and all the Hosts are updated to automatically use TLSv1.2 when upgraded to TIBCO ActiveMatrix 3.4.0, except the Administrator (SystemNode).
Workaround

When you encounter this issue, run the following command after applying TIBCO ActiveMatrix 3.4.0 Hotfix, or upgrading directly to TIBCO ActiveMatrix 3.4.0 Hotfix, in order to update Administrator (SystemNode) to support TLSv1.2.

Go to <TIBCO_HOME>/amx/3.4/bin folder and execute the following command:

tibamx_hostmanager updateAdminToTLSv12 -configHomeLocation <TIBCO_CONFIG_HOME>
Note:
  • Hosts and Nodes MUST be stopped before running the above command. After running the command, restart Administrator (SystemNode).
  • Above command must be executed only on the machine where SystemNode and SystemNodeReplica (if applicable) is running.

In TIBCO ActiveMatrix setup when secure SystemHost and RemoteHosts (Host for which JMX port is secured) are successfully downgraded from TIBCO ActiveMatrix Service Grid 3.4.0, the Administrator UI does not show the updated version of Hosts correctly.

Problem
If SystemHost and RemoteHosts JMX ports are secured after upgrading to TIBCO ActiveMatrix 3.4.0, they use TLSv1.2. When this setup is downgraded, RemoteHosts are automatically updated to use TLSv1 since they use JRE 1.7 after downgrade. However, Administrator (SystemNode) still uses TLSv1.2 to connect to RemoteHosts. Therefore Hosts versions is not updated in Administrator UI.
Workaround
If you encounter this issue after downgrade, update JRE version of all Hosts to JRE 1.8.

Refer to the TIBCO ActiveMatrix Updater Tool for Java Runtime Environment (JRE) Documentation to update the JRE version to JRE 1.8.

After upgrading to TIBCO ActiveMatrix 3.4.0 Hotfix, Administrator version is displayed as 3.4.0 instead of 3.4.0.<Hotfix version>

Problem
  1. TIBCO ActiveMatrix 3.4.0 is installed (without selecting TIBCO ActiveMatrix PD Governance installation profile) to an earlier version of TIBCO ActiveMatrix setup with TIBCO ActiveMatrix Policy Director Governance configured.
  2. TIBCO ActiveMatrix 3.4.0 Hotfix is installed in the same <TIBCO_HOME>.
  3. Upgrade to TIBCO ActiveMatrix 3.4.0 Hotfix fails with the following error:
    product feature com.tibco.governance.gws.product.feature:1.2.0 not found in any local machine model
  4. TIBCO ActiveMatrix 3.4.0 is installed again by selecting only TIBCO ActiveMatrix PD Governance installation profile.
Upgrade to TIBCO ActiveMatrix 3.4.0 Hotfix is successful, but Administrator version is displayed as 3.4.0 instead of 3.4.0.<Hotfix version>.
Workaround
  • If you have installed TIBCO ActiveMatrix Policy Director Governance and already upgraded to TIBCO ActiveMatrix 3.4.0, use the following workaround to apply TIBCO ActiveMatrix 3.4.0 Hotfix:

    Run applyPatch command to apply TIBCO ActiveMatrix 3.4.0 Hotfix in this case. After running applyPatch command Administrator version is displayed as 3.4.0.<Hotfix version>.

  • If you have installed TIBCO ActiveMatrix Policy Director Governance and not upgraded to TIBCO ActiveMatrix 3.4.0 Hotfix then use Workaround A or Workaround B to upgrade to TIBCO ActiveMatrix 3.4.0 Hotfix:

    Workaround A

    1. Install TIBCO ActiveMatrix 3.4.0 Hotfix again.
    2. Upgrade using TIBCO Configuration Tool (TCT).

    Workaround B

    1. Navigate to TIBCO_HOME\amx\<version>\scripts\upgrade and edit tct-upgrade.properties file.
    2. Change the property values as follows:
      amx.platform.patch.version=3.4.0.<Hotfix version>
      amx.node.upgrade.version=3.4.1
    3. Upgrade using TIBCO Configuration Tool (TCT).
Problem
Global Transaction rollback fails on Amazon RDS database.
Workaround
By default max_prepared_transactions is set to 0, and therefore XA is disabled on Amazon RDS database. You must create a new parameter group to set the max_prepared_transactions to a non-zero value and reboot the database. Then the transaction rollback is performed successfully.
Problem
On AIX platform, TIBCO Host fails to start after running the applyPatch command.
./tibamx_hostmanager applyPatch -configHomeLocation /data/AMX340HF6/data -instanceName Admin-amxadmin-instanceOne -ID amx.platform.patch:3.4.0.HF6
Workaround

Update the JRE to JRE 1.8.0 Update 181 or lower and start TIBCO Host again.