Error: 500 Internal Server Error in History or Backlog APIs - Applications Manager
search cancel

Error: 500 Internal Server Error in History or Backlog APIs - Applications Manager

book

Article ID: 449758

calendar_today

Updated On:

Products

Automic Applications Manager

Issue/Introduction

During API testing or standard operations, calls to the History and Backlog APIs return a 500 Internal Server Error. While these specific endpoints fail, other APIs such as Auth, Master, and Agent function as expected.  The spring.log throws error messages "SQL Error: 17026" and "SQLState: 99999".

Symptoms

  • API requests to tasks/history or tasks/backlog return an HTTP 500 response.
  • Spring.log shows error "Could not extract column [2] from JDBC ResultSet [Numeric Overflow]"

  • Full error message below:

    2026-06-30T10:39:27.473-04:00  WARN 1941965 --- [qtp22426187-60] o.h.engine.jdbc.spi.SqlExceptionHelper   : SQL Error: 17026, SQLState: 99999
    2026-06-30T10:39:27.473-04:00 ERROR 1941965 --- [qtp22426187-60] o.h.engine.jdbc.spi.SqlExceptionHelper   : Numeric Overflow
    2026-06-30T10:39:27.475-04:00 ERROR 1941965 --- [qtp22426187-60] c.b.am.server.GlobalExceptionHandler     : Could not extract column [2] from JDBC ResultSet [Numeric Overflow] [n/a]
    org.hibernate.exception.GenericJDBCException: Could not extract column [2] from JDBC ResultSet [Numeric Overflow] [n/a]
     at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:63) ~[hibernate-core-6.6.36.Final.jar!/:6.6.36.Final]
     at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:108) ~[hibernate-core-6.6.36.Final.jar!/:6.6.36.Final]
     at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:94) ~[hibernate-core-6.6.36.Final.jar!/:6.6.36.Final]

Environment

Applications Manager 9.6 to 9.6.2

Cause

The so_aw_seq column in the database endpoint is defined as a 32-bit Integer. The maximum limit for a 32-bit Integer is 2,147,483,647. Once the sequence value exceeds this threshold, the API server encounters a numeric overflow, causing the 500 Server Error.

Resolution

This issue is confirmed as a product defect tracked under DE208291. The fix involves updating the column definition from Integer to Long to support higher sequence values.

Fixed Versions:

  • Applications Manager 9.6.3 and higher.
  • Applications Manager 10.0.0/9.7 and higher (version number no finalized).

Workaround: If an upgrade is not immediately possible, a hotfix is available via an updated api-server.jar.

  1. Download attached api-server.zip and extract api-server.jar.
  2. Stop the Applications Manager services.
  3. Navigate to the API server directory $AW_HOME/lib/java or %AW_HOME%\lib\java (Windows OS) and rename/backup the current api-server.jar.
  4. Replace it with the new api-server.jar.
  5. Restart Applications Manager.

For tracking updates on this defect, subscribe to this article. See how to subscribe to specialized knowledge for more information.

Additional Information

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.

Attachments

api-server.zip get_app