CA TDM Portal High-CPU Utilization

Document ID : KB000045796
Last Modified Date : 14/02/2018
Show Technical Document Details

Issue: 

The CPU will run high for a few minutes when the CA TDM Portal is started while the system is initializing. After the initialization is complete, the system should return to normal. However, in some cases, the CPU utilization will remain high and will not come down.

 

Environment:  

TDM 3.6 or later

 

Cause: 

You can determine when initialization of TDM portal service is complete by monitoring the startup.log file (see section below to locate logs)

Missing QRTZ* tables or lost connections to the Repository DB will cause the TDM Portal to go into an infinite loop, and this will cause the CPU to run at abnormally high levels. 

When used with an Oracle repository database, the high CPU utilization of TDM portal may be also caused because of the limited connection pool size established by Oracle.

 

Resolution:

Take the following diagnostic steps first to correct this problem:

    1. Verify that the Repository DB has the QRTZ* tables. If they are not present, you will need to uninstall and reinstall the TDM Portal.
    2. If the QRTZ* tables are present, but the CPU utilization is still high, try restarting the TDM Portal to re-establish connections to the DB.

 

When working with an Oracle repository: If the below error is observed while trying to start/use the TDM Web Portal (or other TDM components), the system will need to be configured to limit the connections requested by the TDM Portal, and for Oracle to allow more connections.

 

ORA-12516, TNS:listener could not find available handler with matching protocol stack

 

Configuring Connection Pools

Open the application.properties file found in the C:\Program Files\CA\CA Test Data Manager Portal\conf directory, and add the following:

# Connection pool properties (per service)

spring.datasource.initialSize = 5

spring.datasource.minIdle = 5

spring.datasource.maxIdle = 5

spring.datasource.maxActive = 20

spring.datasource.maxWait = 30000

 

Configuring Oracle Resource Limits

Open a sqlplus window, and connect to your repository DB using a system account. For example,

 

SQL> CONNECT system/manager@XE

 

NOTE - The default password used by TDM for the system account is "manager", but the actual password would be set during the installation of Oracle. If you do not have access to the system account, you will need to request that a DBA execute these statements:

 

alter system set processes=300 scope=spfile;

alter system set sessions=300 scope=spfile;

alter system set transactions = 330 scope = spfile;

 

After making the above changes, Oracle and the TDM Portal will need to be restarted. If the same error is still present, you will need to work with the support team for assistance.

 

TDM Portal Log file location

The log file is located by default in the %ProgramData%\CA\CA Test Data Manager Portal\logs folder.

 

Enabling Debug Logging

Debug logs can be enabled by editing the logback-tdm.properties file found in the [installation folder]\conf directory. If you use the default installation folder, this would be C:\Program Files\CA\CA Test Data Manager Portal\conf. You will find a commented out log statement just below the appender section that can be uncommented to turn on all debug logs (or this can be modified to log a subset as desired. Examples are below:

<logger name="com.ca.tdm" level="DEBUG" />

<logger name="com.ca.tdm.jobengine" level="DEBUG" />

 

Additional Information:

Documentation on installing the CA TDM Portal (for TDM 3.6) is available here: https://docops.ca.com/ca-test-data-manager/3-6/en/installing/install-ca-test-data-manager/install-the-ca-tdm-portal