History Service - stderr handling

Current Situation

• If an error occurs during the execution of a job and the controller does not provide additional details about the cause, the History Service captures the first chunk of the potential standard error output (stderr) and stores it to the History database tables as an Error Message.
• In certain scenarios where the stderr contains characters that are not allowed in the current database, such as the NULL character in the case of DBMS PostgreSQL, attempts to write to the database fail.
  • this causes the History Service to stop after several unsuccessful attempts to update the database tables.
    • consequently, this disruption leads to:
      • the History Service no longer works
      • the Controller/Agent log is no longer cleaned up

Test Instructions

• Configure JOC to run against a PostgreSQL database
• Use TEST-JOC-1598.zip
  • Extract the characters.txt file to any location
  • Adapt JOC-1598.workflow.json to use the extracted characters.txt
  • Expected execution result:
    • the workflow execution fails, but the History Service is not stopped and all History entries are available