Bug Fixes

These are the bugs fixed for this version:

6.3.0

General

  • Removed an UnsupportedOperationException that occurred in the ForecastDriver when a combination of older and newer scheduler types were included in a single AAI environment

  • Resolved security vulnerabilities

    Resolved by upgrading spring-framework 4.3.26

    • CVE-2018-1270

    • CVE-2018-1275

    • CVE-2018-15756

    • CVE-2018-1272

    • CVE-2018-1257

    • CVE-2018-11039

    • CVE-2018-11040

    • CVE-2018-1271

    • CVE-2018-1199

    Resolved by upgrading Spring Boot 1.5.22

    • BDSA-2018-1076

    • CVE-2018-1196

    Resolved by upgrading c3p0:JDBC DataSources/Resource Pools 0.9.5.5

    • BDSA-2018-4478

    • CVE-2019-5427

    Connector framework: Resolved by upgrading net.minidev:json-smart to 2.4.2

    • CVE-2021-27568

AutoSys Next Generation

  • Resolved an issue with the Termination Status Report that prevented the statuses that should be included in the report from being available for selection

  • Improved job run linkages to properly link restarted job runs due to job failures into the proper jobstream run

  • Fixed an IllegalArgumentException that occurred when a job failed and then was FORCE_STARTED

Universal Schedulers

  • Fixed an IllegalArgumentException that occurred when Universal job properties were selected from the Columns tab for a Termination Status report

  • Fixed an issue where a user-defined New Predicted Duration for a jobstream run was not correctly reflected in the predicted end time

  • Improved the Universal Jammer so that different events with the same timestamp sent in different transactions from the connector do not result in missed events in AAI

Control-M

Date and Time Processing Failures

Multiple calendar, date, and time processing errors have been fixed. These issues prevented job start time predictions.

  • A missing calendar error occurred due to bad or incomplete smart table data.

  • There was an issue processing previous and next working day schedules for day-of-week and day-of-month calendars.

  • Data center’s daylight savings start and stop times were being incorrectly parsed.

Job/Event Publication Failures

Issues preventing jobs and events from being published to AAI have been fixed.

  • There was an issue when logging job details during error processing.

  • Job publication would fail when jobs had empty or missing job names.

  • The connector was failing to publish events for repeating Control-M Jobs.

  • Event publication was failing due to invalid processing of ‘runinfo_history’ data and causing a circular dependency.

6.3.0-1

General

  • Removed jobstream runs that do not have an end time from the calculations in the Statistics Generator to prevent an IllegalArgumentException which resulted in the Statistics Generator not completing successfully.

  • Resolved security vulnerabilities

  • Resolved by upgrading to bcpkix-jdk15on-168.jar and bcmail-jdk15on-168.jar

    CVE-2018-1000613

    CVE-2018-1000180

    CVE-2020-28052

    CVE-2017-13098

    CVE-2020-26939

AutoSys

  • Fixed an issue with the Simulation feature that resulted in many of the simulated jobstream runs disappearing from the Monitoring tab when delete_job: jobName was used in the JIL definition for the simulation.

  • Resolved an issue that resulted in a simulation ending with a 'Null action' error even with no JIL Definition changes input.

  • Resolved an issue in the JobStreamRunUpdaterImpl process that resulted in a FOREIGN KEY constraint violation (XFKJobRunJobStreamRun_JobRun).

  • Resolved an issue in the JobRunChecker that resulted in a DuplicateJobRunException.

    AAI now catches the exception when updating the job run and increases the jawsNumberRetrys value the same as when submitting a new run.

Tidal

Fixed an issue in the Tidal prediction processing that resulted in a NullPointerException when a Start Job was added to a jobstream.

6.3.0-2

AutoSys

Resolved an issue that resulted in a ConstraintViolationException in theJobStreamRunBuilder after an AAI restart. The issue only occurred when an internal catchup process ran to associate job runs with jobstream runs. The process did not work correctly for Custom AutoSys and resulted in an error like the following: Cannot insert duplicate key row in object 'dbo.JobStreamRun_JobRun' with unique index 'XAK1JobStreamRun_JobRun'. The duplicate key value is (AXhyICAiaNQ=, AXh1XjmQUZM=).

IWS

Resolved an IllegalArgumentException that occurred in AutoSys/IWSz cross-instance environments and resulted in a failure to update with new IWS run events.

Tidal

  • Resolved an issue with the processing of job run events that resulted in a DuplicateJobRunException.

  • Fixed a NullPointerException that occurred in the TidalPredictedJobStreamRunBuilderImpl while associating new job runs with jobstream runs.