KB-1204 "WARNING: exception clearing maxRows/queryTimeout... Invalid operation: statement is closed. ERRORCODE=-4470" error thrown during application server startup

Symptoms

When using Appian with DB2, you could see an error like the following while starting the application server if using an older version of DB2 driver:

2016-06-27 13:56:23,181 [[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'] INFO  com.appiancorp.rdbms.hb.DataSourceManagerHbImpl - [jdbc/AppianPrimaryDS] Search engine initialized successfully: SearchEngineLuceneImpl[LuceneManager[searchIndexDirPath=<APPIAN_HOME>/_admin/search-local/index-primary, unlockSearchIndexWhenUnused=false]]
2016-06-27 13:56:23,199 [[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'] INFO  com.appiancorp.rdbms.hb.DataSourceManagerHbImpl - [jdbc/AppianPrimaryDS] Synchronizing the search index with the database data...
Jun 27, 2016 1:56:23 PM org.hibernate.jdbc.AbstractBatcher closeQueryStatement
WARNING: exception clearing maxRows/queryTimeout
com.ibm.db2.jcc.am.SqlException: [jcc][10120][10943][4.8.117] Invalid operation: statement is closed. ERRORCODE=-4470, SQLSTATE=null
    at com.ibm.db2.jcc.am.gd.a(gd.java:660)
    at com.ibm.db2.jcc.am.gd.a(gd.java:60)
    at com.ibm.db2.jcc.am.gd.a(gd.java:103)
    at com.ibm.db2.jcc.am.zm.xb(zm.java:3952)
    at com.ibm.db2.jcc.am.zm.getMaxRows(zm.java:874)
    .
    .
    .
    <Jun 27, 2016 1:56:23 PM GMT> <Warning> <org.hibernate.jdbc.AbstractBatcher> <BEA-000000> <exception clearing maxRows/queryTimeout
com.ibm.db2.jcc.am.SqlException: [jcc][10120][10943][4.8.117] Invalid operation: statement is closed. ERRORCODE=-4470, SQLSTATE=null
    at com.ibm.db2.jcc.am.gd.a(gd.java:660)
    at com.ibm.db2.jcc.am.gd.a(gd.java:60)
    at com.ibm.db2.jcc.am.gd.a(gd.java:103)
    at com.ibm.db2.jcc.am.zm.xb(zm.java:3952)
    at com.ibm.db2.jcc.am.zm.getMaxRows(zm.java:874)
    Truncated. see log file for complete stacktrace
>
Jun 27, 2016 1:56:23 PM org.hibernate.util.JDBCExceptionReporter logExceptions
WARNING: SQL Error: -4499, SQLState: 58009

Cause

The issue is due to a DB2 driver defect. More details can be found in the following IBM documentation: http://www-01.ibm.com/support/docview.wss?uid=swg21598736

Action

Update the database driver to a supported version, depending on the DB2 version you are using. More information can be found in System Requirements.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2017