You are currently reviewing an older revision of this page.

SP-4611 Database calls fail with "Connection has already been closed" for on-premise installations

Symptoms

After an upgrade or after new database calls are configured for an on-premise installation, calls to the database from the application server fail and the following error is seen in the application server log:

ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit
java.sql.SQLException: Connection has already been closed.

Cause

Databases have a default timeout period after which connections are deemed "idle" and terminated, causing the application server to be unable to make calls to the database.

Action

Increase the value of  removeAbandonedTimeOut in tomcat-resources.xml so that it is set to the longest running query your application may have.

Affected Versions

This article applies to Appian 19.1 and later.

Last Reviewed: August 2020