AutoSys Web Server does not start after AutoSys upgrade

Products

• Autosys Workload Automation

Issue/Introduction

AEWS log, waae_webservices_wrapper.log contains errors like:

STATUS | wrapper  | 2026/05/30 17:57:14 | Launching a JVM...
INFO   | jvm 1    | 2026/05/30 17:57:14 | OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
INFO   | jvm 1    | 2026/05/30 17:57:14 | WrapperManager: Initializing...
INFO   | jvm 1    | 2026/05/30 17:57:14 | WrapperManager: ERROR - The version of the Wrapper which launched this JVM is "3.5.41"
INFO   | jvm 1    | 2026/05/30 17:57:14 | WrapperManager:         while the version of the Wrapper jar file currently in use
INFO   | jvm 1    | 2026/05/30 17:57:14 | WrapperManager:         is "3.5.51".
INFO   | jvm 1    | 2026/05/30 17:57:14 | WrapperManager:
INFO   | jvm 1    | 2026/05/30 17:57:14 | WrapperManager: ERROR - The version of the Wrapper which launched this JVM is
INFO   | jvm 1    | 2026/05/30 17:57:14 | WrapperManager:         "3.5.41-st" while the version of the native library
INFO   | jvm 1    | 2026/05/30 17:57:14 | WrapperManager:         is "3.5.51-st".
INFO   | jvm 1    | 2026/05/30 17:57:14 | WrapperManager:

 

Bad server had $AUTOSYS/bin/wrapper  with  Nov 29 2020  time stamp.  Another server where it works fine, had one dated Sep 2023 

Cause

In this specific situation, during upgrade, a custom monitoring program was restarting the webserver when it was supposed to have been shutdown for upgrade. This left the wrapper in use, there by the file did not get replaced during the upgrade.

Resolution

Copy $AUTOSYS/bin/wrapper from good server to bad one and restart webserver service.