AAI 24.4.0-1 Upgrade: Connection to Schedulers Lost Due to Altered Connection Strings

Products

• Automation Analytics & Intelligence

Issue/Introduction

After upgrading Automation Analytics & Intelligence (AAI) to version 24.4.0-1, the following symptoms may occur:

• AAI loses connection to some job schedulers.
• The Jammer fails for affected schedulers with the following error in jaws.log: WARN [RunCycle] Jammer failed for scheduler: [SchedulerName] java.lang.NullPointerException: Cannot invoke "com.termalabs.common.hibernate.jaws.SchedulerConnection.getServer()" because "connectionDefinition" is null.
• When attempting to edit the scheduler in the Web UI, the following error is displayed: Cannot invoke "com.termalabs.common.hibernate.jaws.SchedulerConnection.getCustomConnectionUrl()" because the return value of "com.termalabs.common.hibernate.jaws.JobScheduler.getPrimaryConnection()" is null.

Cause

During the upgrade to 24.4.0-1, the encrypted connection strings in the jobScheduler database table are incorrectly altered or corrupted. This prevents the application from retrieving the necessary server and connection definitions, causing the NullPointerException.

Resolution

Workaround & Pre-Upgrade Steps

To mitigate this issue or restore functionality after an upgrade, follow these steps:

Before Upgrading

To ensure a recovery path, all customers must perform the following before starting the upgrade to 24.4.0-1:

1. Full Database Backup: Create a complete backup of the AAI database.
2. Export Scheduler Table: Run the following query and save the output (e.g., to a CSV file) to preserve the original connection strings:
   sql

   SELECT * FROM jobScheduler;

3. Backup Configuration Files: Secure a copy of the .jawsey file from the AAI configuration directory.

If Already Upgraded

If the upgrade has already been completed and connection details are missing:

1. Stop the AAI application services.
2. Restore the AAI database from the pre-upgrade backup
3. Or update the jobscheduler table to enter your connection details again in the jobscheduler table, and restart.  Please work with AAI Support to format this SQL for your scheduler
4. Ensure the pre-upgrade .jawsey file is in place.
5. Restart AAI services and verify that scheduler connections are restored in the Web UI.