ARD 3.1.1.4 - GTService sporadically shutsdown when running ALM Export

Products

• CA Agile Requirements Designer

Issue/Introduction

 

 

After applying the ARD 3.1.1.4 patch, we have started seeing sporadic behavior with the GTService, where the service sporadically shuts down when running make data, and exporting test cases to ALM. This behavior does not happen for ARD 3.1.0.2.

We have tested the TDMService, and so far that service seems to be stable and does not shutdown with ARD 3.1.1.4. However, we are reluctant to putting the 3.1.1.4 patch into production, until we understand why it introduced this unexpected behavior.

For now our users are still running ARD 3.1.0.2, which still has the problem of Make Data variables not being saved properly after a flow is closed. Therefore, we need to understand the cause of this odd behavior, so that we are comfortable putting the 3.1.1.4 patch in production.

Environment

Release : 3.1

Component : CA Agile Requirements Designer

Cause

Suspected Cause:

ARD 3.1.1.4 has some additional code to take care of sending variables from subflows.

ARD 3.1.0.2 doesn’t send any variables mapped in subflows to the ADGLink file, which was a reported defect.

The problem was found to be with some legacy flows, which were set up for ALM exports long before ARD 3.1.1.4. When we tried to resolve variables related to subflow, which referred to other TDoD flows (mapped in past), but no longer in use, and thus causing GTService to shut down when attempting to resolve subflow variables that do not exist anymore. 

Resolution

Manually checked each subflow to ensure mapping with TDoD flows are correct, and ensure the GTService is not brought down.

The long term preventative solution is to upgrade TDM to TDM 4.9.1 or greater, and use the TDMService, which is a more modern service, and supported by the TDM Engineering team.