History Service - Filtering of offending characters in Error Messages

Current Situation

• The JOC Cockpit History Service receives messages from a Controller and Agent that can include output created by jobs. Such output can contain characters that cannot be stored by some DBMS, for example 0-Bytes cannot be stored to a PostgreSQL database.
• The character filtering applied to the stderr in the context of the JOC-1598 issue is insufficient, given that these characters can come from various other sources (e.g. Outcome.Failed)

Desired Behavior

• Filtering should be applied to the complete Error Message.

Patch
Patches are available for:

• Release 2.5.5
  • https://download.sos-berlin.com/patches/2.5.5-patch/js7_joc.2.5.5-PATCH.API-1.JOC-1649.jar
• Release 2.6.2
  • https://download.sos-berlin.com/patches/2.6.2-patch/js7_joc.2.6.2-PATCH.API-1.JOC-1649.jar

Test Instructions

• Configure JOC to run against a PostgreSQL database
• Use Test-JOC-1598-1649.zip
  • Extract the characters-<*>.txt files to any location
  • Adapt JOC-15981649.workflow.json to use the extracted characters-<*>.txt
    • the workflow consists of 3 jobs:
      1. JOC-1598
         • JOC-1598 functionality testing
      2. JOC-1649-JS7_RETURN_VALUES-OK
         • the job execution should succeed and the return values should be created (check the log output of this job)
      3. JOC-1649-JS7_RETURN_VALUES-NOK
         • the job execution fails, but the History Service is not stopped and all History entries are available
  • Expected execution result:
    • the workflow execution fails due to last job, but the History Service is not stopped and all History entries are available