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.

JCP loops and crashes when using search

book

Article ID: 237242

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Under some circumstances the AWI search function can lead to a loop in the JCP (REST). 

The JCP log shows the following:

20220316/075756.400 - 37     U00029131 UCUDB - List of bind parameters:
20220316/075756.400 - 37     U00009907 Memory dump '(BINDPAR:  1)' (Address='n/a', Length='000004')
20220316/075756.401 - 37               00000000  00000000                             >....<
20220316/075756.401 - 37                                             >0<
20220316/075756.401 - 37     U00009907 Memory dump '(BINDPAR:  2)' (Address='n/a', Length='000004')
20220316/075756.401 - 37               00000000  0000000E                             >....<
20220316/075756.402 - 37                                             >14<
20220316/075756.402 - 37     U00009907 Memory dump '(BINDPAR:  3)' (Address='n/a', Length='000004')
20220316/075756.402 - 37               00000000  00000000                             >....<
20220316/075756.402 - 37                                             >0<
20220316/075756.403 - 37     U00009907 Memory dump '(BINDPAR:  4)' (Address='n/a', Length='000004')
20220316/075756.403 - 37               00000000  0000000E                             >....<
20220316/075756.403 - 37                                             >14<
20220316/075756.403 - 37     U00003525 UCUDB: ===> 'select AH.AH_Idnr, null as AH_ERTEnd, AJPP.AJPP_Object, AJPP.AJPP_OType, AJPP.AJPP_Lnr, AJPPA.AJPPA_PreLnr, AH.AH_Ert, AH.AH_Runtime, AH.AH_TimeStamp2, AH.AH_TimeStamp4, AJPP.AJPP_JobStatus, AJPP.AJPP_AH_Idnr, 0 as AH_LoopIteration, AJPPF.AJPPF_LoopCount, AJPPF.AJPPF_LoopIterator, AJPP.AJPP_SubType, AH.AH_TimeStamp1, AJPP.AJPP_ErlstStTime from ah left join ajpp on ah.ah_parentprc = ajpp.ajpp_ah_idnr and ah.ah_ajpp_lnr = ajpp.ajpp_lnr left join ajppa on ajpp.ajpp_ah_idnr = ajppa.ajppa_ah_idnr and ajpp.ajpp_lnr = ajppa.ajppa_ajpp_lnr left join ajppf on ah.ah_parentprc = ajppf.ajppf_ah_idnr where ah.ah_parentprc = ? and ah.ah_client = ? union all select AH.AH_Idnr, null as AH_ERTEnd, AH.AH_Name, AH.AH_OType, AH.AH_AJPP_Lnr, AJPPA.AJPPA_PreLnr, AH.AH_Ert, AH.AH_Runtime, AH.AH_TimeStamp2, AH.AH_TimeStamp4, AH.AH_Status, 0 as AH_ParentHir, 0 as AH_LoopIteration, AJPPF.AJPPF_LoopCount, AJPPF.AJPPF_LoopIterator, AH.AH_SubType, AH.AH_TimeStamp1, null as AJPP_ErlstStTime from ah left join ajpp on ah.ah_parentprc = ajpp.ajpp_ah_idnr and ah.ah_ajpp_lnr = ajpp.ajpp_lnr left join ajppa on ajpp.ajpp_ah_idnr = ajppa.ajppa_ah_idnr and ajpp.ajpp_lnr = ajppa.ajppa_ajpp_lnr left join ajppf on ah.ah_parentprc = ajppf.ajppf_ah_idnr where ah.ah_idnr = ? and ah.ah_client = ? '
===
20220316/075757.131 - 37               no root item found for workflow with runID: 0
20220316/075758.310 - 37               WorkflowStructureItem{runId=106919717, ertEnd=null, objectName='null', objectType='null', objectSubType='null', lnr=null, predecessorLnr=null, ertInSeconds=2291, rrtInSeconds=226559, startTime=2021-03-09 14:29:01.0, endTime=2021-03-12 05:25:00.0, status=null, parentRunId=null, childLoopIndex=0, loopIndex=null, loopCount=null, activationTime=2021-03-09 14:28:53.0, earliestStartTime=null, topNr=null}
20220316/075758.310 - 37               WorkflowStructureItem{runId=106923179, ertEnd=null, objectName='null', objectType='null', objectSubType='null', lnr=null, predecessorLnr=null, ertInSeconds=2291, rrtInSeconds=226092, startTime=2021-03-09 14:36:02.0, endTime=2021-03-12 05:24:14.0, status=null, parentRunId=null, childLoopIndex=0, loopIndex=null, loopCount=null, activationTime=2021-03-09 14:35:55.0, earliestStartTime=null, topNr=null}
<... 452K lines ...>
20220316/081014.841 - 201              WorkflowStructureItem{runId=140861036, ertEnd=null, objectName='null', objectType='null', objectSubType='null', lnr=null, predecessorLnr=null, ertInSeconds=0, rrtInSeconds=0, startTime=2022-03-16 07:01:06.0, endTime=2022-03-16 07:01:07.0, status=null, parentRunId=null, childLoopIndex=0, loopIndex=null, loopCount=null, activationTime=2022-03-16 07:01:06.0, earliestStartTime=null, topNr=null}
20220316/081014.841 - 201              WorkflowStructureItem{runId=140861037, ertEnd=null, objectName='null', objectType='null', objectSubType='null', lnr=null, predecessorLnr=null, ertInSeconds=0, rrtInSeconds=0, startTime=2022-03-16 07:01:12.0, endTime=2022-03-16 07:01:12.0, status=null, parentRunId=null, childLoopIndex=0, loopIndex=null, loopCount=null, activationTime=2022-03-16 07:01:12.0, earliestStartTime=null, topNr=null}
20220316/081224.800 - 206    U00003449 Output to the TRACE file is finished.
20220316/081224.801 - 193    U00003524 UCUDB: ===> Time critical DB call!       OPC: 'WAIT' time: '292089ms'
20220316/081224.802 - 185    U00003620 Routine 'com.automic.rest.provider.BaseExceptionMapper' forces trace because of error.
20220316/081224.803 - 202    U00003524 UCUDB: ===> Time critical DB call!       OPC: 'WAIT' time: '290262ms'
20220316/081224.803 - 29     U00003406 Client connection '21'  from '172.18.88.7:48948' has logged on to the Server.
20220316/081224.803 - 206    U00045099 The server replied with following status: '500'
20220316/081224.812 - 185    U00003450 The TRACE file was opened with the switches '0000000000000000'.
20220316/081226.755 - 185    U00003449 Output to the TRACE file is finished.
20220316/081226.755 - 185    U00045099 The server replied with following status: '500'

In the JCP traces, we can find:


20220503/095521.811 - 47               ----------------------- Stack Trace -----------------------
20220503/095521.812 - 47               java.lang.OutOfMemoryError: Java heap space

Cause

This is defect

Environment

Release : 12.3.x and 21.0.x

Component : AUTOMATION ENGINE

Resolution

Workaround:

To prevent the JCP from crashing increase the memory of the JCP (REST) to 2 GB during startup (-Xmx2048m) or higher (-Xmx4096m) if still occurring.

Solution:

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

Fix version:

Component(s): Automation Engine

Automation.Engine 21.0.2 HF1 - Available
Automation.Engine 21.0.3 - Planned release May 2022
Automation.Engine 12.3.9 - Planned release June 2022