When a Monitor of any Scheduler or Workflow is opened all WPs crashes immediately

Document ID : KB000087789
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
N/A

When a Monitor of any Scheduler or Workflow is opened all WPs crashes immediately!
 
This happens in case of:
  • The operation system where the Automation Engine Server (WPs) is running is UNIX. Linux is not affected.
  • The Automation Engine Server (WPs) wars updated to version 11.2.x.
 
In the trace the last transaction logged it the "getmonitor", it reads one EJPP and it crashes:
 
20160718/111354.330 - UCDS_R                RCV  <eh      frm *CP001#00000012 107  getmonitor           MQ1CP001 MsgID: 0052323111 c-acv: 0000000020160718/111354.336 -                                        >318094586<20160718/111354.336 - /*XREQ*/Select * from EH where EH_AH_Idnr = ?                                00000000  4A534348                             >JSCH<20160718/111354.339 - U00009909 TRACE: (DB-DATEN: EH_OH_Idnr        )             9001000a44c1f54 00000420160718/111354.339 -                                        >1076019<20160718/111354.339 - U00009909 TRACE: (DB-DATEN: EH_AH_Idnr        )             9001000a44c2024 00000420160718/111354.339 -                                        >318094586<20160718/111354.349 -                                        >318094586<20160718/111354.349 - /*XREQ*/Select * from EJPP where EJPP_AH_Idnr = ? order by EJPP_Lnr                                00000000  4A4F4253                             >JOBS<                                00000000  5543342E 4A4F4253 2E554E49 582E4348  >UC4.JOBS.UNIX.CH<                                00000010  45434B5F 54494D45 4F5554             >ECK_TIMEOUT<20160718/111354.352 - U00009909 TRACE: (DB-DATEN: EJPP_SubType      )             9001000a44c5474 00000020160718/111354.352 - UCUDB32 READ RET 0000 HSTMT: 000000011008c7b0 VALUE: 000000000000000e ALL:  0.00133 DB:  0.00021 ODBC:  0.00000 UDB:  0.0011220160718/111354.352 - UCUDB32 INIT RET 0000 HSTMT: 0000000000000000 VALUE: 0000000000000000 ALL:  0.00001 DB:  0.00000 ODBC:  0.00000 UDB:  0.0000120160718/111354.352 - UCUDB32 FLDT RET 0000 HSTMT: 0000000000000000 VALUE: 0000000000000000 ALL:  0.00001 DB:  0.00000 ODBC:  0.00000 UDB:  0.0000120160718/111354.352 - UCUDB32 FLDG RET 0000 HSTMT: 0000000000000000 VALUE: 0000000000000000 ALL:  0.00001 DB:  0.00000 ODBC:  0.00000 UDB:  0.0000120160718/111354.352 - UCUDB32 FLDT RET 0000 HSTMT: 0000000000000000 VALUE: 0000000000000000 ALL:  0.00000 DB:  0.00000 ODBC:  0.00000 UDB:  0.0000020160718/111354.352 - UCUDB32 FLDG RET 0000 HSTMT: 0000000000000000 VALUE: 0000000000000000 ALL:  0.00000 DB:  0.00000 ODBC:  0.00000 UDB:  0.0000020160718/111354.352 - UCUDB32 FLDT RET 0000 HSTMT: 0000000000000000 VALUE: 0000000000000000 ALL:  0.00000 DB:  0.00000 ODBC:  0.00000 UDB:  0.0000020160718/111354.352 - UCUDB32 FLDG RET 0000 HSTMT: 0000000000000000 VALUE: 0000000000000000 ALL:  0.00000 DB:  0.00000 ODBC:  0.00000 UDB:  0.0000020160718/111354.352 - UCUDB32 FLDT RET 0000 HSTMT: 0000000000000000 VALUE: 0000000000000000 ALL:  0.00000 DB:  0.00000 ODBC:  0.00000 UDB:  0.0000020160718/111354.352 - UCUDB32 FLDG RET 0000 HSTMT: 0000000000000000 VALUE: 0000000000000000 ALL:  0.00000 DB:  0.00000 ODBC:  0.00000 UDB:  0.0000020160718/111354.352 - UCUDB32 FLDT RET 0000 HSTMT: 0000000000000000 VALUE: 0000000000000000 ALL:  0.00000 DB:  0.00000 ODBC:  0.00000 UDB:  0.0000020160718/111354.352 - UCUDB32 FLDG RET 0000 HSTMT: 0000000000000000 VALUE: 0000000000000000 ALL:  0.00000 DB:  0.00000 ODBC:  0.00000 UDB:  0.0000020160718/111354.352 - UCUDB32 FLDT RET 0000 HSTMT: 0000000000000000 VALUE: 0000000000000000 ALL:  0.00001 DB:  0.00000 ODBC:  0.00000 UDB:  0.0000120160718/111354.352 - UCUDB32 FLDG RET 0000 HSTMT: 0000000000000000 VALUE: 0000000000000000 ALL:  0.00001 DB:  0.00000 ODBC:  0.00000 UDB:  0.00001

 
Other symptoms:
  • There is no quarantine message created, but a core dump is taken by the operating system (depending on the ulimit settings).
  • The Service Manger logs show:
U00022022 Der Prozess 'UC4 WP1' wurde beendet, Exitcode='1(-1)'.
 
 
No workaround found, yet! Not opening any Monitor, is not an acceptable one!
The root cause is kind of a buffer overrun, which causes the WP to fail.
 
Cause:
Cause type:
Defect
Root Cause: The root cause is kind of a buffer overrun, which causes the WP to fail.
Resolution:
This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.

Fix Status: Released

Fix Version(s):
AE Server and Initialdata 11.2.2 HF2 of Automation.Engine - already available
Additional Information:
Workaround :
No workaround found, yet!(Not opening any Monitor, is not an acceptable one!)