Java NoClassDefFoundError: com/ca/autosys/services/JJobResRsp when migrating to AutoSys 24.x

Products

• Autosys Workload Automation

Issue/Introduction

Custom-coded Java applications that functioned correctly with AutoSys 12.x SDK/APIs may fail when executed against an AutoSys 24.x environment. The application terminates with a java.lang.NoClassDefFoundError or java.lang.ClassNotFoundException.

Error Message:

Plaintext

 

Exception in thread "main" java.lang.NoClassDefFoundError: com/ca/autosys/services/JJobResRsp 
        at com.ca.autosys.services.JResponse.create(Native Method)
        at com.ca.autosys.services.JResponse.<init>(JResponse.java:83)
        at com.ca.autosys.services.response.GetGlobalsRspSet.dequeueResponse(GetGlobalsRspSet.java:58)
        at com.ca.autosys.services.response.ApiResponseSet.hasNext(ApiResponseSet.java:69)
...
Caused by: java.lang.ClassNotFoundException: com.ca.autosys.services.JJobResRsp

Environment

 

• Source Version: AutoSys Workload Automation 12.x

• Target Version: AutoSys Workload Automation 24.x

• Component: Java SDK / API (asapi.jar)

 

Resolution

The internal structure and class mappings within the AutoSys API have been updated in version 24.x. Custom applications compiled against the 12.x version of the SDK are not binary compatible with the 24.x runtime environment if they reference classes that have moved or changed.

To resolve this issue:

1. Rebundle/Recompile: Update the project dependencies in your development environment to use the 24.x asapi.jar.

2. Rebuild: Recompile and rebundle the custom application to ensure it correctly references the classes as they exist in the 24.x release.