Error U02013310: RA JD Edwards Agent fails to start with Microsoft JDBC driver on SQL Server 2022
search cancel

Error U02013310: RA JD Edwards Agent fails to start with Microsoft JDBC driver on SQL Server 2022

book

Article ID: 451295

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

When attempting to configure the RA JD Edwards Agent to use the official Microsoft JDBC driver (e.g., mssql-jdbc-12.x.x.jre11.jar) instead of the legacy jTDS driver, the agent fails to start.

The agent logs show the following error sequence:

Error connecting to the database. Check the JDBC login assigned to the agent and verify that it is correct.Error: Cannot invoke "Object.getClass()" because "connection" is nullU02013310 Failed to load RA Agent.

Environment

Automic Automation Engine 24.x
RA JD Edwards Agent 2.2.9 and below
RA Core 24
Microsoft SQL Server 2022

Cause

The RA JD Edwards Agent (along with other RA-based agents like RA OEBS) contains an explicit internal check that requires the use of the jTDS driver for MS SQL Server connections.

Per the java.sql.Driver.connect() contract, the JTDS driver returns null if it does not recognize the URL. Because the agent expects a JTDS-style URL (jdbc:jtds:sqlserver://...), providing a Microsoft-style URL (jdbc:sqlserver://...) causes the connection to return null, leading to a NullPointerException (NPE) and agent shutdown.

Resolution

Currently, only the built-in jTDS driver is supported for the RA JD Edwards Agent when connecting to Microsoft SQL Server.

  1. Continue using the jTDS 1.3.1 driver for all MS SQL Server connections.
  2. Ensure the Connection URL in the AWI Connection Object follows the format: jdbc:jtds:sqlserver://<hostname>:<port>/<dbname>.

If you are interested in the support for the official Microsoft JDBC driver, please open a Request for Enhancement (RFE) through the Broadcom Support Portal. This requires a change to the underlying RA framework to remove the explicit jTDS driver check.

Additional Information

For more information on configuring JDBC objects, refer to the .

Note: To stay updated on any future changes regarding driver compatibility, please subscribe to this article