Release notes for RunMyJobs releases 2024.1.1.0 through to 2024.1.1.1

Before: In 2024.1.0.0, users without edit privilege for an object, would see a popup with an HTTP 500 error when attempting to edit that object.

After: Users see the edit page with a warning on top that they cannot edit that page.

Before : System_MonitorTablesSubmitFrame and System_SynchronizeBackgroundJobsSubmitFrame was not working as expected.

After : System_MonitorTablesSubmitFrame and System_SynchronizeBackgroundJobsSubmitFrame now updated to run once per day.

Current Behavior: No ad-hoc alert was being raised when operator message for the job was already served.

New Behavior: Now an ad-hoc alert will be sent per ad-hoc alert source for the job.

Before: The default value of DatabaseRetries configuration was 18 and the max value was 45.

After: Both values have been updated. Now the default value is 100 and the max value is 1000.

Before: the upgrade logic for deduplicating process definition parameter display order could slow down the upgrade process significantly.

After: this code has been optimised.

Before: the DB2 JDBC driver that was shipped with the product contained the following vulnerabilities: CVE-2023-27859, CVE-2023-45193, CVE-2023-47141, CVE-2023-47145, CVE-2023-47152, CVE-2023-47158, CVE-2023-47746, CVE-2023-47747, CVE-2023-50308

After: the driver has been upgraded from version 11.5.7.0 to 11.5.9.0, which resolves these issues.

Before:
jgetfile uses a fixed connection timeout of 10 minutes.
After:
Commandline parameter -timeout <seconds> is added to jgetfile to enable setting the connection read/write timeout. The default value is still set at 600 seconds (10 minutes).

Before: Vulnerability scanners sending excessively large chunk transfer encoding or excessively large Content-Length HTTP requests to a Platform Agent would result in ambiguous StringBuffer maximum capacity exceeded FATAL messages being logged.

After: Vulnerability scanners sending excessively large HTTP requests to a Platform Agent now result in clear ERROR messages being logged.

Before: Platform Agent was built with OpenSSL version 3.0.9
After: Platform Agent is built with OpenSSL version 3.0.13

Before:
Startup of Platform Agent on Unix systems, could hang if there are no older version directories present.
The log file would repeatedly show the following line in debug mode:
DEBUG 2024-02-23 13:29:47,318 CET 12044-sendmessage-9 #3 opsys.dir - Creating directory /opt/redwood/agent/.lock

After:
Platform agents starts up normally when there are no older versions present to be cleaned up.

Before: the PostgreSQL JDBC Driver (version 42.5.3) that was shipped with RMJ contained CVE-2024-1597.

After: the PostgreSQL JDBC Driver was updated to version 42.7.2, which contains a fix.

Before:
The interface showed an error in case that no "/configuration/jcs/ui/helpurl" registry entry was defined. This impacted the “Preview new UI button”.

After:
Default registry value will be used and no error occurs when previewing the new UI.

Before: Showing the details page of a Job Definition with a huge source could potentially cause the browser to crash.

After: The Source of a Job Definition shown on its detail page is truncated to 100,000 characters, preventing the browser running out of memory. The full Source is still visible on the edit page of the Job Definition. As a side effect this makes these detail pages more performant, both when opening and when performing actions.

Before: File events on Linux could be missed, (most likely) when the creation timestamp of these files were in the future.
This caused that such files would not be picked up by the notification system anymore when the file had ‘aged’.

After: Files events are picked up and handled as before, using the polling mechanism.