CA TDM Portal Troubleshooting

If you installed the TDM Portal in the default location, the path is C:\Program Files\CA\CA Test Data Manager Portal\. If you installed the portal in a non-default location, adjust the paths on this page accordingly.
tdm43
If you installed the TDM Portal in the default location, the path is 
C:\Program Files\CA\CA Test Data Manager Portal\
. If you installed the portal in a non-default location, adjust the paths on this page accordingly.
 
 
2
 
 
TDM portal seems to hang when I confirm large tables on the Data Model page
Symptom:
When I view the PII scan data of a large Data Model (around 2000 tables), and click the Confirm button on the data model page to confirm all tables, the Portal becomes unresponsive.
TDM Portal passes the table identifiers through a request header, and due to the large number of tables, the request header size surpasses the default size that is defined for the Apache Tomcat server. The server rejects such a large request and it the Portal becomes unresponsive.
Solution:
Increase the maxHttpHeaderSize setting in Tomcat's server.xml.
  1. From Windows Explorer, open the file
    C:\Program Files\CA\CA Test Data Manager Portal\tomcat\conf\server.xml
    in a text editor.
  2. To add the
    maxHttpHeaderSize
    attribute, do
    one
    of the following tasks:
    • If you are using HTTPS or port 8443, then add
      maxHttpHeaderSize="3000000"
      as attribute of the
      <Connector port="8443">
      element.
      Example:
      <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true" scheme="https" secure="true" clientAuth="false" sslProtocol="TLSv1.2" keystoreFile="${tdmweb.keystorePath}" keystorePass="${tdmweb.keystorePassword}" keyAlias="${tdmweb.keyAlias}" ciphers="TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_DHE_RSA_WITH_AES_256_GCM_SHA384,TLS_DHE_RSA_WITH_AES_128_GCM_SHA256" connectionTimeout="60000"
      maxHttpHeaderSize=“3000000"
      />
    • If you are using HTTP or port 8080, then add
      maxHttpHeaderSize="3000000"
      as attribute of the
      <Connector port="8080">
      element.
      Example:
      <Connector port="8080" protocol="HTTP/1.1" connectionTimeout="60000"
      maxHttpHeaderSize="3000000"
      />
  3. Restart the TDM Portal service.
Jobs artifacts not being downloaded in Portal
 
Symptom:
 
My jobs artifacts are not being downloaded in the CA TDM Portal.
 
Solution:
 
Verify whether you have multiple portal instances pointing to one repository (GTREP). If yes, create a separate GTREP database for each CA TDM Portal Installation, and reinstall the CA TDM Portal instances so that each has a 1:1 mapping to its own GTREP database.
Decrease High CPU Utilization
It is normal behavior that CPU usage runs high for a few minutes when the TDM Portal starts while the system is initializing. After the initialization is complete, the system load returns to normal. Monitor the 
startup.log
 file to determine when initialization is complete.
 
Symptom
 
CPU runs at abnormally high levels even after initialization is complete.
 
Reason
 
Missing QRTZ* tables or lost connections to the Repository DB cause the TDM Portal to go into an infinite loop, which causes high CPU load.
 
Solution
 
Take the following diagnostic steps to end the loop:
  1. Verify that the Repository DB has the QRTZ* tables. 
  2. If the QRTZ* tables are not present, uninstall and reinstall the TDM Portal.
  3. If the QRTZ* tables are present, but the CPU is still high, restart the TDM Portal to re-establish connections to the DB.
Configure Resource Constraints for Oracle Repositories
 
Symptom
 
You observe the following error when you start or use the CA TDM Web Portal, or other CA TDM components:
ORA-12516, TNS:listener could not find available handler with matching protocol stack
 
 
Solution
 
Configure the system to limit the connections that are requested by the TDM Portal, and to allow more connections for Oracle databases.
Configure Oracle Resource Limits
  1. Open a sqlplus window, and connect to your repository DB using a system account as 
    sysdba
    The default password that TDM uses for the system account is "manager", but you set the actual password when you install Oracle. If you do not have access to the system account, request that a DBA execute the statements.
    For example, for a local XE installation, you connect as follows:
    SQL> CONNECT [email protected]/manager as sysdba  
     
  2. Run the following commands to verify the parameters values:
    show parameter processes
    show parameter session
    show parameter transactions
  3. The following are the recommended values. If your values are less than the recommended values, use the following commands:
    alter system set processes=300 scope=spfile;
    alter system set sessions=300 scope=spfile;
    alter system set transactions=330 scope=spfile;
  4. Save the file.
  5. Restart Oracle and the TDM Portal.
If the same error reoccurs, work with the support team for assistance.
Unable to log in to the CA TDM Portal
 
Symptom
 
When I try to log in to the CA TDM Portal, I receive the following error in the Portal despite entering correct credentials:
 
Incorrect username and password
 
Also, when I review the
%ProgramData%\CA\CA Test Data Manager Portal\logs\TdmWeb.log
file, I find the following entry in the log file:
 
Could not write content: An attempt was made to write more data to the response headers than there was room available in the buffer. Increase maxHttpHeaderSize on the connector or write less data into the response headers
 
 
Solution
 
If you try to log in to the Portal that includes a large number of projects, you can receive this error and the log entry, despite providing correct credentials. 
To address this issue, increase the maximum size of the request and response HTTP header (
maxHttpHeaderSize
) as follows:
  1. Navigate to the 
    C:\Program Files\CA\CA Test Data Manager Portal\tomcat\conf
     location.
  2. Open the 
    server.xml
     file in a text editor.
  3. Add the 
    maxHttpHeaderSize
     parameter to the following section:
    <Connector port="8443" protocol="HTTP/1.1".......maxHttpHeaderSize="2000000"/>
    The value
    2000000
    bytes is provided as an example. You can enter the value depending on your requirements. 
     The default value of the request and response HTTP header is 8000 bytes.
  4. Save your changes.
  5. Restart the CA Test Data Manager Portal service.
Unable to Publish Data in the CA TDM Portal
 
Symptom
 
I am unable to publish the data in the CA TDM Portal. 
 
Solution
 
One of the reasons could be that you do not have access to the appropriate security functions. Verify with your CA TDM Portal administrator about whether your user profile has privileges to publish the data.
Unable to Install the Portal After Manual Uninstall
 
Symptom
 
I uninstalled the CA TDM Portal by manually deleting the files. Now, when I am trying to install it again, I am unable to do so. 
 
Solution
 
We recommend that you do not manually uninstall the CA TDM Portal. In the case of manual uninstall, it is possible that the Portal fails to uninstall properly, leaving behind a few registry entries or services. To correct this failure scenario:
  • Ensure that Windows services has no CA TDM Portal service in it. If it exists, remove it.
  • Ensure that no related keys are present in the registry entries. For example, if the following keys exist, the installer picks them to verify the old products. Therefore, delete them:
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ComputerAssociates\CA Test Data Manager Portal
    HKEY_CURRENT_USER32\Software\Caphyon\Advanced Installer\LZMA\{
    <ID>
    }
    HKEY_LOCAL_MACHINE32\Software\Caphyon\Advanced Installer\LZMA\{
    <ID>
    }
Receiving Insufficient Privileges Error
 
Symptom
 
I am getting the following error in the CA TDM Portal:
 
Access Denied. You do not have sufficient permissions to access this content.
 
 
Solution
 
If a user receives this type of error message in the CA TDM Portal, it might be the case that the UI session of the user does not have the updated privileges to the resources. In such cases, users must log out from and then log in to the CA TDM Portal to get the updated privileges and continue their work. If you still receive this error, contact the CA TDM Portal administrator to understand whether you have sufficient privileges to access the resource.
Find Log Files
The log file location has been moved from the TDM Portal installation folder to the following ProgramData folder: 
 
%ProgramData%\CA\CA Test Data Manager Portal\logs\
 
 The easiest way to monitor the log files is to download a free utility, for example, BareTail.
Another option is to use a Powershell script with the following properties:
 
$APPROOT = $Env:CATDMWEB_APPDATA $WEBLOGS = "$APPROOT\logs"
Get-Content -Path "$WEBLOGS\tdmweb.log" -Wait
 
Enable Debug Logging
If you are experiencing any issues with the CA TDM Portal, and want more information of the most probable cause, review the log files for details. You can set the log level to DEBUG. This can be very helpful to find out where things are going wrong.
The logs of all the Portal services running in the background are created as soon as the Portal is up and running. The Portal supports these log levels: TRACE, DEBUG, INFO, WARN, and ERROR. Out of these levels, the DEBUG level is best suited to get as much information as possible in the log files.
 
Follow these steps:
 
  1. Navigate to the
     C:\Program Files\CA\CA Test Data Manager Portal\conf
     directory. 
  2. Open the 
    logback-tdm.xml
     file in a text editor.
  3. Find the commented-out log statement below the appender section.
  4. Uncomment the statement to enable debug logs. Do one of the following:
    1. Enable all debug logs.
      <logger name="com.ca.tdm" level="DEBUG" />
       
    2. Modify the statement to log only a subset of the application.
      <logger name="com.ca.tdm.jobengine" level="DEBUG" /> 
       
  5. Restart the CA Test Data Manager Portal service.
Monitor the JVM Activity of the TDM Portal
You can observe memory, threads, and other performance characteristics of the TDM Portal JVM. To monitor the JVM activity of the TDM Portal, use JMX to connect to the JVM. 
 
To enable JMX, follow these steps:
 
  1. Navigate to the 
    C:\Program Files\CA\CA Test Data Manager Portal\service\conf
     folder.
  2. Open the 
    wrapper.conf
     file in a text editor.
  3. Add the following lines to the Java Additional Parameters section:
    wrapper.java.additional.
    7
    =-Dcom.sun.management.jmxremote
    wrapper.java.additional.
    8
    =-Dcom.sun.management.jmxremote.port=
    31417
    wrapper.java.additional.
    9
    =-Dcom.sun.management.jmxremote.authenticate=false
    wrapper.java.additional.
    10
    =-Dcom.sun.management.jmxremote.ssl=false
  4. Adjust the numbered suffixes in the parameter names to match your parameter list. 
  5. Modify the port number as needed for your requirements.
  6. Save the file.
  7. Restart the TDM Portal service.
  8. Use JConsole to connect on the port that you just specified as additional parameter.
Publish Data to Sybase IQ Database
To successfully publish data to Sybase IQ database from TDM Portal, ensure that you have modified the corresponding database configuration file (.cfg) in the Sybase IQ installed server for the following parameters:
  • Modify the parameter 
    -c 48m
     to 
    -c 64m
     
  • Modify the parameter 
    -gm 10
     to 
    -gm 30
     
  • Add the parameter 
    -gn 45
     at the end of the file
After modifying the configuration file (.cfg) of the corresponding database, restart the Sybase IQ database.
Submitted Requests in TDM Portal Waits for 30 Seconds to Start Running
 
Symptom
 
When I submit a request in CA TDM Portal, the status of the request remains as "Not Started" for 30 seconds. Despite refreshing the page, the status does not change to "Running" for 30 seconds.
 
Reason
This happens because the repository database has a Quartz Configuration of Idle Wait Time property set to 30000 milliseconds by default. Idle Wait Time is the amount of time in milliseconds that the scheduler will wait before picking up a request from the queue. 
 
Solution
You can edit the Quartz Configuration to set the Idle Wait Time that suits your requirements.
Follow these steps:
  1. Open the 
    quartz_oracle.properties
     file or the
     quartz_sqlserver.properties 
    file based on the repository database you are using. These files are typically available under the path 
    C:\Program Files\CA\CA Test Data Manager Portal\tomcat\webapps\TDMJobService\WEB-INF\classes\.
     
  2. Find the parameter 
    org.quartz.scheduler.idleWaitTime=30000
     in the file. If the parameter is not available add the same at the end of the file.
  3. Modify the value 30000 to a lesser value that you want to set as Idle Wait Time in milliseconds. Save the File.
  4. Restart the CA TDM Portal Service.
    Notes:
    1. Values less than 5000 milliseconds are not recommended as it will cause excessive database querying. Values less than 1000 are not legal.
    2. Any modifications to the Quartz configuration are not retained after upgrading the CA TDM Portal. You must modify the values manually after the upgrade.
    For more information see Quartz Configuration Reference documentation currently available at http://www.quartz-scheduler.org/documentation/quartz-2.1.x/configuration/ConfigMain.html.
Previous Version Artifacts Not Working in the Latest Version
 
Symptom
 
I uninstalled my existing CA TDM Portal instance and then installed the latest version. Now, my artifacts that I created in my previous version (uninstalled now) are not working in the latest version. For example, when I try to perform the export RR (request-response) pair operation in the CA TDM Portal 4.0 for the work done in the CA TDM Portal 3.8, I receive a NULL pointer exception.
 
Solution
 
If you uninstall the existing CA TDM Portal installation and install the latest version, the existing OrientDB database is also uninstalled and the one that comes with the latest CA TDM Portal version gets installed. This creates issues because all the artifacts created in the previous CA TDM Portal installation and stored in the associated OrientDB database are lost. These artifacts, therefore, no longer work in the latest installation, resulting in an additional effort for you to recreate them. 
To overcome this issue, you can simply upgrade the CA TDM Portal. This way, you can avoid the unnecessary work of recreating the artifacts that you created for use in the previous release of the CA TDM Portal.
However, if you must uninstall the CA TDM Portal, ensure that you take a backup of the OrientDB database before uninstallation, so that you can preserve your work artifacts.
Connection Manager Service Failing (404 Not Found Error)
 
Symptom
 
When I try to perform a publish operation in the CA TDM Portal, I get the following error:
 
ERROR: Publish failed for job ***, Call to ConnectionManagerService failed::HttpClientErrorException: 404 Not Found
 
 
Solution
 
Create the associated connection profiles in the CA TDM Portal. Additionally, associate them with the user group that is connected to the CA TDM Portal (when publishing the data).
Connection Manager Service Failing (403 Forbidden Error)
 
Symptom
 
When I try to perform a publish operation in the CA TDM Portal, I get the following error:
 
Call to ConnectionManagerService failed::HttpClientErrorException: 403 Forbidden
 
 
Solution
 
This error is linked to the fact that you did not authorize your user to use this connection profile. For this, you must associate your user group with the connection profile used by your user.
TCP/IP Connection to the Host Failed
 
Symptom
 
I am receiving the following error in the CA TDM Portal:
 
The TCP/IP connection to the host ***, port 1433 has failed.
Error: "connect timed out.
Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port.
Make sure that TCP connections to the port are not blocked by a firewall.
 
How can I address this issue?
 
Solution
 
Check your Microsoft SQL server connection and Windows or network firewall.
If you are using SQL Server Express, then this error could be because this server uses dynamic ports by default. In this case, you can try to solve the error by following one of the following ways:
  • Specify the instance and no ports in the CA TDM Portal configuration. 
  • Configure the static port in your SQL Server Express configuration manager instead of the dynamic ones.