Release notes for RunMyJobs releases 2023.3.0.0 through to 2023.3.0.5

Before: When using an independent constraint parameter as first parameter a NPE occured.

After: This has been resolved.

Before: It could be that an error message was shown that we didn’t fill in mandatory parameters when LOV’s should find the display values in huge EBS chains.

After: This has been fixed.

Before: When PeopleSoft jobs are deleted that are monitored by RMJ, RMJ ignored the removed message. When the Job is killed within RMJ the killed job is not removed from monitoring.

After: This has been fixed.

Before: The eclipse plugin failed to import process definitions, failing with an InvocationTargetException.

After: The eclipse plugin imports process definitions successfully

Before: during import, the invalidate on error flag is not propagated to child job.

After: the invalidate on error flag is propagated to child import jobs

Before: When upgrading past 9.2.10, for any job that had an expression on chain parameter to change the start time of the call, then these jobs would be skipped after the upgrade. Once they have been run once, then any subsequent run would work correctly.

After: After the update, all calls are update to set the RequestedStartTimeType from UserSet to SchedulingParameter, for jobs in statuses Chained, Held and New. This update is run once.

NOTE: Since it is not possible to determine if the ScheduledStartTime was really set by the user or not, and this is rarely done, all calls in statuses Chained, Held and New get updated.

Before: setting an output value on a non-string parameter via Job File Search was not possible

After: it is now also possible to map Job File Search results to non-string parameters

Before: importing autoinstallable car files errors out when there are conflicting dependencies on the imported library
After: the import will set the invalidate flag on the import to force the import to succeed and invalidate the conflicting dependent libraries

Before: System_Info in a clustered environment throws a NotSerializableException

After: There is no exception on System_Info in a clustered environment

Before: the clustering logic could, in rare circumstances, end up throwing an exception while comparing two exceptions for “sameness”.

After: the exception will no longer be thrown.

Before: Redwood application upgrade fails from version 2023.2.0.0 to 2023.3.0.0 if SqlServer database is a case sensitive.

After: This should be resolved.

SAP JCo has been updated to the latest 3.1.8 release.

Before:
When platform agent operates in sudo-mode, running a job as different user would log the following error message:
Unable to open lockfile ‘/opt/redwood/agent/var/<RW_platform>/<instance>/jobs/12/3456/lock'
The executed job itself was unaffected by this error and still succeeded.

After:
Running the job as different user in sudo-mode platform agent will not raise the 'Unable to open lockfile’ error anymore.

Before: Platform agent upgrade was not keeping the most recent unused version, due to incorrect sorting.
After: Platform agent is now keeping the most recent unused version as spare again after upgrade.

Before: SAP Process Servers can start when no Spool Host is defined but is required.

After: SAP Process Server do not start when Spool Host is required but not present

Before: SAP BObj connector did not properly recognize wrong credentials. Connection check would not return any result.

After: Check Bobj connection throws error message when using wrong credentials

Before: SAP BOBJ processes can potentially end up in an endless loop when session id gets invalidated

After: Always get new session id if the old one gets invalid.

Before: Existing SAP variant values were removed if they were not explicitly filled during SAP job submission

After: Existing SAP variant values are preserved if they are not filled during SAP job submission.

Before: the admin server database export fails on the object search condition table

After: the admin server database export succeeds

Before: CVE-2023-42503 in Apache Commons Compress was present in several of our extension points.

After: The vulnerability has been addressed by an upgrade to version 1.24.0.

Before: RunMyJobs was using Tomcat 9.0.75, in which a security issue has been found (CVE-2023-41080)

After: Tomcat has been upgraded to 9.0.80, where the security issue is resolved.

NOTE: The configuration of RunMyJobs precludes the vulnerability, however the version is being upgraded out of precaution.

Before: RMJ was running on Tomcat 9.0.80, which is vulnerable to CVE-2023-44487, CVE-2023-45648, CVE-2023-42795, and CVE-2023-42794.

After: RMJ is now hosted on Tomcat 9.0.82, which is the latest release and without known vulnerabilities.

NOTE: The configuration of RunMyJobs limits the impact of these vulnerabilities, making the believed risk of exploitation low, however the version is being upgraded out of precaution.

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: Extend print parameters PRCMP, ALVSL, ALVST, MXLSZ, UCDISPL are not supported

After: Extend print parameters PRCMP, ALVSL, ALVST, MXLSZ, UCDISPL can be added manually into duplicated SAP_AbapRunPrint/SAP_AbapRunPrintExt process definition.

Before: List-Of-Values query was executed on EBS database, as soon as a parameter field of an EBS Process Definition was activated.
After: It is now possible to add a minimum required value length for a parameter, before the List-Of-Values query is executed in the EBS database.
The minimum length can set set as a new section in the Process Definition, specifying the parameter filed and its minimum required length, e.g.

[MinimumParameterLength]
(Low) Bill To Customer Name=3
(High) Bill To Customer Name=5

Before: When the configuration for retrieving the EBS files is not correctly setup the job will stay in Running phase and error messages are written to the scheduler.log file.

After: When the file can’t be retrieved an jobNote is attached to the job and the job is put into Error.

Before: when a wildcard was used in a Job File Search, the generated Job Note did not indicate the actual file the lookup was found in

After: the full filename in which the lookup was found is now reported in the generated Job Note

Before:
All RMJ threads ran at priority 5 (normal) apart from Redwood Dispatcher Agent which ran at 8 (a higher priority),
by default, controlled by the /configuration/jcs/dispatcher/ThreadPriority configuration setting.
This meant that at times of heavy loads, with a lot of Runnable Java threads at the same priority, the UI response would be slow.

After:
All four RMJ Dispatcher threads are now controlled by the DispatcherPriority configuration setting, and will run at priority 8 by default. This configuration setting is now available in multiple backends, for the RMJ registry this will be /configuration/jcs/core/DispatcherPriority configuration setting . The RMJ registry setting /configuration/jcs/dispatcher/ThreadPriority is now deprecated.

The priority of UI threads is now controlled by Redwood Platform container environment variable RP_HTTP_NIO_THREAD_PRIORITY, and by default UI threads run at priority 9.
You can view the thread priorities under Support page https:/<server>:<port>/<contextURL>/support/info

Notes
Java thread priorities run from 1 (lowest) through 5(normal) to 10 (highest)

Before: When Registry Entry changes are made that are associated with configuration settings, no validation on the provided value takes place, as well as user permission verification.

After: User permission verification and value validation is done before Registry Entry value are changed that are associated with a configuration option.

Before: It was not possible to provide a locale for parsing numbers in a SAP spool file

After: It is now possible to provide a locale for parsing numbers in a SAP spool file

It is now possible to define if a variant is of type online or background

Before: Opening a simple JobChain editor on a system with a lot of Applications could potentially take a long time.

After: Opening a simple JobChain editor on a system with a lot of Applications is now fast.