Traces are generated with the following message. The generation of those traces does not have any impact on the performance of the JWP.
20250427/020009.766 - 36 INSERT INTO RH (RH_AH_IDNR,RH_ARCHIVEFLAG,RH_BLKSIZE,RH_CLIENT,RH_DELETEFLAG,RH_FILEINDB,RH_FILEONAGENT,RH_TimeStamp1,RH_Type,RH_USERSLOGIN,RH_XMLFLAG) VALUES (?,?,?,?,?,?,?,?,?,?,?)20250427/020009.782 - 36 UCUDB32 EXEC RET 0001 HSTMT: 0000000001386905 VALUE: 0000000000000000 ALL: 0.01600 DB: 0.00000 ODBC: 0.00000 UDB: 0.0000020250427/020009.783 - 36 UCUDB32 CLST RET 0000 HSTMT: 0000000001386905 VALUE: 000000000000000020250427/020009.784 - 36 U00003590 UCUDB - DB error: '23503', 'ERROR: insert or update on table "rh" violates foreign key constraint "fk_rh_ah"20250427/020009.784 - 36 Detail: Key (rh_ah_idnr)=(57283306) is not present in table "ah".', '0', 'org.postgresql.util.PSQLException'20250427/020009.785 - 36 SQL Statement which caused this DB error:20250427/020009.785 - 36 U02012075 Set bind parameter '1' of type 'Integer' to value '57283306'
Automation Engine 24.2.0, 24.3.0, and 24.4.0
Java processes may write a forced trace because of a foreign key violation of "fk_rh_ah".
Fixed in Automation Engine 24.4.1