AWI throws OSGi Framework errors when using unsupported Java versions during upgrade to 21.0

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation

Issue/Introduction

During an upgrade to Automic Web Interface (AWI) version 21.0.15, users are unable to log in. The AWI log displays the following error:

unable to detect used OSGi framework version due to Cannot invoke "org.osgi.freamwork.Bunder.getVersion()" because "osgiBundle" is null

Environment

• Product: CA Automic Workload Automation - Automation Engine
• Component: Automic Web Interface (AWI)
• Version: 21.0.x

Cause

This issue occurs when the AWI is launched using an unsupported Java version. For example, if the default Java version on the server is Java 17, the AWI may fail because version 21.0 is only compatible with Java 8 or Java 11.

Resolution

To resolve this issue, the AWI must be started using a supported Java version (Java 8 or Java 11).

1. Identify the path to the supported Java executable (e.g., C:\Program Files\java\{java 8 or 11 version}\bin\java).
2. Launch the AWI by pointing directly to this Java path using a command similar to the following: "C:\Program Files\java\{java 8 or 11 version}\bin\java" -jar aa-webui-launcher.jar
3. Log in to the AWI to verify that the system is operational.
4. Ensure your server environment or startup scripts are updated to use the correct Java version consistently.