Error: Invalid HttpClientPojo version on AutoSys Agent 24.1 post upgrade

Products

• Workload Automation Agent

Issue/Introduction

After upgrading a Workload Automation Agent to version 24.1 and installing plugin extensions such as Databricks and DBT, POJO jobs may fail with an "Invalid HttpClientPojo version" error.

Environment

Workload Automation Agent 24.1
AutoSys Workload Automation
Databricks Plugin Extension
DBT Plugin Extension

Cause

Legacy versions of common SDK JAR files (dated December 2024 or earlier) remain in the agent root `jars` directory after an upgrade. The agent classloader prioritizes files in the `jars` folder over those in the `jars/ext` directory. If a legacy library like `httpclientpojo-3.3.2.jar` exists in the root, it overrides the required version 3.7.0 in the extension path.

Symptoms

• Jobs that previously worked on Agent 12.1 fail with status FA (Failure) immediately after starting.
• Agent logs or job output contain the error: <Invalid HttpClientPojo version>.
• cybAgent -vv output shows the correct plugin versions (e.g., Databricks 1.0.21, HTTP Client POJO SDK 3.7.0), but job execution still fails.
• autoping and agent status checks are successful.

Resolution

Remove the duplicate legacy libraries from the agent root directory to resolve the version conflict:

1. Stop the AutoSys Agent.
2. Navigate to the jars directory (the root JAR folder, not the jars/ext folder).
3. Identify and move the following legacy files to a temporary backup directory outside of the Agent path:httpclientpojo-####.jar
   
   • authenticationsdk-####.jar
   • jakarta.json-api-####.jar
   • jakarta.json-####.jar
   • parsson-####.jar
   • pluginscommon-####.jar
   • xmljsonparser-####.jar
4. [Optional] For consistency purposes, if there are differences in permissions for the new jars as compared to existing jars, standardize permissions for the remaining JAR files in both the jars and jars/ext directories to conform with your organizations requirements.
5. Restart the Agent.

Additional Information

If further assistance is needed, please refer to our main Contact Broadcom Support article.