ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
AE produces a large number of flush ring traces, when a workflow is cancelled
Article ID: 132168
CA Automic Workload Automation - Automation Engine
When cancelling a workflow, the Automation Engine starts generating minimal trace and the following errors may be seen in the logs:
U00011801 Fehler in Serverroutine 'JPEXEC_R', Server: 'UC4#WP007' AE-System: 'UC4'. U00003513 UCUDB: Not all HSTMT were closed: Quantity = '1' U00009907 Dump 'Exception in message handler java.lang.IllegalArgumentException: null' (address = 'n / a', length = '000147') U00009907 Dump 'Exception in message handler java.nio .BufferUnderflowException: null '(address =' n / a ', length =' 000164 ') U00005118 Program error: DB access to key 'EH_AH_Idnr' with value 0 in module 'UCGENX_R'. U00003620 Routine 'UCGENX_R' opens forced tracing due to errors.
This is due to an internal database statement not closing properly.
Release: Component: AAUTEN
The issue was found and fixed with:
Automation.Engine 12.0.8 in AutomationEngine - released 5-6-2019 Automation.Engine 12.1.5 in AutomationEngine - pending release Automation.Engine 12.2.3 in AutomationEngine - pending release Automation.Engine 12.3.0 in AutomationEngine - pending release
Hotfix-Description: Forced traces at workflow-end.
An error has been fixed where the AutomationEngine creates forced traces during end-processing of workflows if the workflow is cancelled. Error message is: "U00011801 Error in Server-routine 'JPEXEC_R', Server: 'UC4#WP007' AE-System: 'UC4'."