Upgrade to TDM 4.11, Subset are now failing with “Job has stalled (its status was 'Running' on engine startup)”

Products

• CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

After upgrading from 4.10 to 4.11.2016.0 Portal, Data Generator for one of existing project (Subset from DB to DB) is not running now and failed with the message “Job has stalled (its status was 'Running' on engine startup)” after 12hrs of run without providing any log data.

 We are also running in Java Heap errors.

 

 

Environment

TDM 4.11.2016

Cause

The Java release has been upgraded in TDM 4.11 to Java 17. Beginning in TDM 4.11.1001 we have added additional features, which have increased the memory requirements for Java while the micro-services are starting.

Resolution

Here are some recommendations based on the above issue:  

1. Reduce the number of Cached items in SQL list 
# the number of rows that will be cached for a table that has 'actualCols' columns:
#   cached rows = sqllistCachedRows /
tdmweb.TDMService.sqllistCachedRows=150000

2. Use % Total RAM setting for Min and Max Memory. 
 Instead of configuring the min and max memory heap size, configure the % of memory it will use.
# % of total RAM
wrapper.java.initmemory.relative=30
# % of total RAM
wrapper.java.maxmemory.relative=70