CP Trace is not fully deactivated after trace file is finished

Article Id: 84438
Status: Published
Updated On: 15-04-2018 08:00
Legacy Id: 000013686
Products:
CA Automic Workload Automation - Automation Engine AUTOMIC WORKLOAD AUTOMATION
Issue/Introduction:

Error Message :
N/A

After deactivating trace options set for the CP's the tracing is not stopped although the tracing is turned off.
The Automation Engine has the trace files still in use and writes some information to the Trace file.

Investigation

Example:

  1. Set a trace on a system for one CP similar to this: TCP/IP=2 and DB=4 
  2. Wait a bit and then set the trace flags back to something like this TCP/IP=0 and DB=0 and apply the changes 
  3. Now execute a simple script or start an Agent
  4. The trace file will now includes this information although the tracing was turned off prior to the activity in step 3.
Results

Expected: The Trace file is finished, no longer in use by a Worker Process (WP) and not extended with information after the tracing is turned off

Actual:The Trace file is finished, however, it is still in use by a Worker Process (WP) and information is added to the files although the tracing is turned off

Cause:

Cause type:
Defect
Root Cause: Trace for CP is still written, even if it is turned off.

Environment:

OS Version: N/A

Resolution:

Update to a fix version listed below or a newer version if available.

Fix Status: Released

Fix Version(s):
Automation Engine 12.1.1 - Available
Automation Engine 12.0.4 - Available

Additional Information:

Workaround :
Restart the CP on which the Tracing was enabled.