https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environmentsen-USTelligent Community 12https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environmentsMon, 17 Aug 2020 14:45:11 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b5e56291-2097-494f-8f6a-61dc1975074aElly Menghttps://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments#commentsCurrent Revision posted to Appian Knowledge Base by Elly Meng on 8/17/2020 2:45:11 PM<br /> <h2>Symptoms</h2> <p>After an upgrade or after new database calls are configured for an self-managed installation, calls to the database from the application server fail and the<span>&nbsp;following error&nbsp;is seen in the application server log:</span></p> <pre class="code-java">ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit java.sql.SQLException: Connection has already been closed.</pre> <h2>Cause</h2> <p>The database connection has been abandoned since the query ran for more than the allotted time configured&nbsp;in&nbsp;<code><span>removeAbandonedTimeOut</span></code> (the default value is 60s).</p> <h2>Action</h2> <p><span>Increase the value of&nbsp;<code>removeAbandonedTimeOut</code></span>&nbsp;in&nbsp;<strong>tomcat-resources.xml&nbsp;</strong>so that it is set to the longest running query the application may have.</p> <h2>Affected Versions</h2> <p>This article applies to Appian&nbsp;19.1 and later.</p> <p>Last Reviewed: August 2020</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: database, application server, timeout, upgrade, infrastructure</div> https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments/revision/20Mon, 17 Aug 2020 14:33:21 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b5e56291-2097-494f-8f6a-61dc1975074aElly Menghttps://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments#commentsRevision 20 posted to Appian Knowledge Base by Elly Meng on 8/17/2020 2:33:21 PM<br /> <h2>Symptoms</h2> <p>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<span>&nbsp;following error&nbsp;is seen in the application server log:</span></p> <pre class="code-java">ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit java.sql.SQLException: Connection has already been closed.</pre> <h2>Cause</h2> <p>The database connection has been abandoned since the query ran for more than the allotted time configured&nbsp;in&nbsp;<code><span>removeAbandonedTimeOut</span></code> (the default value is 60s).</p> <h2>Action</h2> <p><span>Increase the value of&nbsp;<code>removeAbandonedTimeOut</code></span>&nbsp;in&nbsp;<strong>tomcat-resources.xml&nbsp;</strong>so that it is set to the longest running query the application may have.</p> <h2>Affected Versions</h2> <p>This article applies to Appian&nbsp;19.1 and later.</p> <p>Last Reviewed: August 2020</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: database, application server, timeout, upgrade, infrastructure</div> https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments/revision/19Mon, 17 Aug 2020 14:33:03 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b5e56291-2097-494f-8f6a-61dc1975074aElly Menghttps://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments#commentsRevision 19 posted to Appian Knowledge Base by Elly Meng on 8/17/2020 2:33:03 PM<br /> <h2>Symptoms</h2> <p>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<span>&nbsp;following error&nbsp;is seen in the application server log:</span></p> <pre class="code-java">ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit java.sql.SQLException: Connection has already been closed.</pre> <h2>Cause</h2> <p>The database connection has been abandoned since the query ran for more than the allotted time configured&nbsp;in&nbsp;<code><span>removeAbandonedTimeOut</span></code> (<code><span>t</span></code>he default value is 60s).</p> <h2>Action</h2> <p><span>Increase the value of&nbsp;<code>removeAbandonedTimeOut</code></span>&nbsp;in&nbsp;<strong>tomcat-resources.xml&nbsp;</strong>so that it is set to the longest running query the application may have.</p> <h2>Affected Versions</h2> <p>This article applies to Appian&nbsp;19.1 and later.</p> <p>Last Reviewed: August 2020</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: database, application server, timeout, upgrade, infrastructure</div> https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments/revision/18Mon, 17 Aug 2020 13:45:28 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b5e56291-2097-494f-8f6a-61dc1975074aKritesh Arorahttps://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments#commentsRevision 18 posted to Appian Knowledge Base by Kritesh Arora on 8/17/2020 1:45:28 PM<br /> <h2>Symptoms</h2> <p>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<span>&nbsp;following error&nbsp;is seen in the application server log:</span></p> <pre class="code-java">ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit java.sql.SQLException: Connection has already been closed.</pre> <h2>Cause</h2> <p>The database connection has been abandoned since the query ran more than the time configured for <code><span>removeAbandonedTimeOut</span></code>. The default value is 60s.</p> <h2>Action</h2> <p><span>Increase the value of&nbsp; <code>removeAbandonedTimeOut&nbsp;</code></span>in&nbsp;<strong>tomcat-resources.xml&nbsp;</strong>so that it is set to the longest running query your application may have.</p> <h2>Affected Versions</h2> <p>This article applies to Appian&nbsp;19.1 and later.</p> <p>Last Reviewed: August 2020</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: database, application server, timeout, upgrade, infrastructure</div> https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments/revision/17Mon, 17 Aug 2020 13:45:03 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b5e56291-2097-494f-8f6a-61dc1975074aKritesh Arorahttps://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments#commentsRevision 17 posted to Appian Knowledge Base by Kritesh Arora on 8/17/2020 1:45:03 PM<br /> <h2>Symptoms</h2> <p>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<span>&nbsp;following error&nbsp;is seen in the application server log:</span></p> <pre class="code-java">ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit java.sql.SQLException: Connection has already been closed.</pre> <h2>Cause</h2> <p>The database connection has been abandoned since the query ran more than the time configured for <span>removeAbandonedTimeOut</span>. The default value is 60s.</p> <h2>Action</h2> <p><span>Increase the value of&nbsp; <code>removeAbandonedTimeOut&nbsp;</code></span>in&nbsp;<strong>tomcat-resources.xml&nbsp;</strong>so that it is set to the longest running query your application may have.</p> <h2>Affected Versions</h2> <p>This article applies to Appian&nbsp;19.1 and later.</p> <p>Last Reviewed: August 2020</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: database, application server, timeout, upgrade, infrastructure</div> https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments/revision/16Mon, 17 Aug 2020 13:44:47 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b5e56291-2097-494f-8f6a-61dc1975074aKritesh Arorahttps://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments#commentsRevision 16 posted to Appian Knowledge Base by Kritesh Arora on 8/17/2020 1:44:47 PM<br /> <h2>Symptoms</h2> <p>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<span>&nbsp;following error&nbsp;is seen in the application server log:</span></p> <pre class="code-java">ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit java.sql.SQLException: Connection has already been closed.</pre> <h2>Cause</h2> <p>The database connection has been abandoned since the query ran more than the time configured for&nbsp;removeAbandonedTimeout. The default value is 60s.</p> <h2>Action</h2> <p><span>Increase the value of&nbsp; <code>removeAbandonedTimeOut&nbsp;</code></span>in&nbsp;<strong>tomcat-resources.xml&nbsp;</strong>so that it is set to the longest running query your application may have.</p> <h2>Affected Versions</h2> <p>This article applies to Appian&nbsp;19.1 and later.</p> <p>Last Reviewed: August 2020</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: database, application server, timeout, upgrade, infrastructure</div> https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments/revision/15Mon, 17 Aug 2020 13:42:45 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b5e56291-2097-494f-8f6a-61dc1975074aKritesh Arorahttps://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments#commentsRevision 15 posted to Appian Knowledge Base by Kritesh Arora on 8/17/2020 1:42:45 PM<br /> <h2>Symptoms</h2> <p>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<span>&nbsp;following error&nbsp;is seen in the application server log:</span></p> <pre class="code-java">ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit java.sql.SQLException: Connection has already been closed.</pre> <h2>Cause</h2> <pre><span>The database connection has been abandoned since the query ran more than time specified for&nbsp;removeAbandonedTimeout.</span></pre> <h2>Action</h2> <p><span>Increase the value of&nbsp; <code>removeAbandonedTimeOut&nbsp;</code></span>in&nbsp;<strong>tomcat-resources.xml&nbsp;</strong>so that it is set to the longest running query your application may have.</p> <h2>Affected Versions</h2> <p>This article applies to Appian&nbsp;19.1 and later.</p> <p>Last Reviewed: August 2020</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: database, application server, timeout, upgrade, infrastructure</div> https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments/revision/14Fri, 07 Aug 2020 17:09:29 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b5e56291-2097-494f-8f6a-61dc1975074aElly Menghttps://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments#commentsRevision 14 posted to Appian Knowledge Base by Elly Meng on 8/7/2020 5:09:29 PM<br /> <h2>Symptoms</h2> <p>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<span>&nbsp;following error&nbsp;is seen in the application server log:</span></p> <pre class="code-java">ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit java.sql.SQLException: Connection has already been closed.</pre> <h2>Cause</h2> <p><span>Databases have a default timeout period after which connections are deemed &quot;idle&quot; and terminated, causing the a</span>pplication server to be unable to make calls to the database.</p> <h2>Action</h2> <p><span>Increase the value of&nbsp; <code>removeAbandonedTimeOut&nbsp;</code></span>in&nbsp;<strong>tomcat-resources.xml&nbsp;</strong>so that it is set to the longest running query your application may have.</p> <h2>Affected Versions</h2> <p>This article applies to Appian&nbsp;19.1 and later.</p> <p>Last Reviewed: August 2020</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: database, application server, timeout, upgrade, infrastructure</div> https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments/revision/13Fri, 07 Aug 2020 17:07:24 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b5e56291-2097-494f-8f6a-61dc1975074aElly Menghttps://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments#commentsRevision 13 posted to Appian Knowledge Base by Elly Meng on 8/7/2020 5:07:24 PM<br /> <h2>Symptoms</h2> <p>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<span>&nbsp;following error&nbsp;is seen in the application server log:</span></p> <pre class="code-java">ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit java.sql.SQLException: Connection has already been closed.</pre> <h2>Cause</h2> <p><span>Databases have a default timeout period after which connections are deemed &quot;idle&quot; and terminated, causing the a</span>pplication server to be unable to make calls to the database.</p> <h2>Action</h2> <p><span>Increase the value of&nbsp; <code>removeAbandonedTimeOut&nbsp;</code></span>in&nbsp;<strong>tomcat-resources.xml&nbsp;</strong>so that it is set to the longest running query your application may have.</p> <h2>Affected Versions</h2> <p>This article applies to Appian&nbsp;19.1 and later.</p> <p>Last Reviewed: August 2020</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: database, application server, timeout, upgrade, infrastructure</div> https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments/revision/12Fri, 07 Aug 2020 17:04:57 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b5e56291-2097-494f-8f6a-61dc1975074aElly Menghttps://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments#commentsRevision 12 posted to Appian Knowledge Base by Elly Meng on 8/7/2020 5:04:57 PM<br /> <h2>Symptoms</h2> <p>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<span>&nbsp;following error&nbsp;is seen in the application server log:</span></p> <pre class="code-java">ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit java.sql.SQLException: Connection has already been closed.</pre> <h2>Cause</h2> <p><span>Databases have a default timeout period after which connections are deemed &quot;idle&quot; and terminated, causing the a</span>pplication server to be unable to make calls to the database.</p> <h2>Action</h2> <p><span>Increase the value of&nbsp; <code>removeAbandonedTimeOut&nbsp;</code></span>in&nbsp;<strong>tomcat-resources.xml&nbsp;</strong>so that it is set to the longest running query your application may have.</p> <h2>Affected Versions</h2> <p>This article applies to Appian&nbsp;19.1 and later.</p> <p>Last Reviewed: August 2020</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: database, application server, timeout, upgrade, infrastructure</div> https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments/revision/11Fri, 07 Aug 2020 16:57:06 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b5e56291-2097-494f-8f6a-61dc1975074aElly Menghttps://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments#commentsRevision 11 posted to Appian Knowledge Base by Elly Meng on 8/7/2020 4:57:06 PM<br /> <h2>Symptoms</h2> <p>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<span>&nbsp;following error&nbsp;is seen in the application server log:</span></p> <pre class="code-java">ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit java.sql.SQLException: Connection has already been closed.</pre> <h2>Cause</h2> <p><span>Databases have a default timeout period after which connections are deemed &quot;idle&quot; and terminated, causing the a</span>pplication server to be unable to make calls to the database.</p> <h2>Action</h2> <p><span>Increase the value of&nbsp; <code>removeAbandonedTimeOut&nbsp;</code></span>in&nbsp;<strong>tomcat-resources.xml&nbsp;</strong>so that it is set to the longest running query your application may have.</p> <h2>Affected Versions</h2> <p>This article applies to Appian&nbsp;19.1 and later.</p> <p>Last Reviewed: August 2020</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: database, application server, timeout, upgrade, infrastructure</div> https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments/revision/10Fri, 07 Aug 2020 14:50:12 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b5e56291-2097-494f-8f6a-61dc1975074aElly Menghttps://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments#commentsRevision 10 posted to Appian Knowledge Base by Elly Meng on 8/7/2020 2:50:12 PM<br /> <h2>Symptoms</h2> <p>After an upgrade for an on-premise installation, calls to the database from the application server fail and the<span>&nbsp;following error&nbsp;is seen in the application server log:</span></p> <pre class="code-java">ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit java.sql.SQLException: Connection has already been closed.</pre> <h2>Cause</h2> <p><span>Databases have a default timeout period after which idle connections are terminated, causing the a</span>pplication server to be unable to make calls to the database.</p> <h2>Action</h2> <p><span>Increase the value of&nbsp; <code>removeAbandonedTimeOut&nbsp;</code></span>in&nbsp;<strong>tomcat-resources.xml</strong>.</p> <h2>Affected Versions</h2> <p>This article applies to Appian&nbsp;19.1 and later.</p> <p>Last Reviewed: August 2020</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: database, application server, upgrade, infrastructure</div> https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments/revision/9Tue, 14 Jul 2020 17:29:51 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b5e56291-2097-494f-8f6a-61dc1975074aKritesh Arorahttps://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments#commentsRevision 9 posted to Appian Knowledge Base by Kritesh Arora on 7/14/2020 5:29:51 PM<br /> <h2>Symptoms</h2> <p>Calls to the database from the app server fail after an upgrade for an on-premise installation.&nbsp;<span>The following error can be seen in the application server log:</span></p> <pre class="code-java">ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit java.sql.SQLException: Connection has already been closed.</pre> <h2>Cause</h2> <p><span>Databases have a default timeout period after which idle connections are terminated, causing the a</span>pp server to be unable to make calls to the database.</p> <h2>Action</h2> <p><span>Increase the value of&nbsp; <code>removeAbandonedTimeOut&nbsp;</code></span>in&nbsp;<strong>tomcat-resources.xml</strong>.</p> <h2>Affected Versions</h2> <p>This article applies to Appian&nbsp;19.1 and later.</p> <p>Last Reviewed: June 2020</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: database, application server, upgrade, infrastructure</div> https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments/revision/8Tue, 14 Jul 2020 17:29:15 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b5e56291-2097-494f-8f6a-61dc1975074aKritesh Arorahttps://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments#commentsRevision 8 posted to Appian Knowledge Base by Kritesh Arora on 7/14/2020 5:29:15 PM<br /> <h2>Symptoms</h2> <p>Calls to the database from the app server fail after an upgrade or migration to another virtual machine or server for an on-premise installation.&nbsp;<span>The following error can be seen in the application server log:</span></p> <pre class="code-java">ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit java.sql.SQLException: Connection has already been closed.</pre> <h2>Cause</h2> <p><span>Databases have a default timeout period after which idle connections are terminated, causing the a</span>pp server to be unable to make calls to the database.</p> <h2>Action</h2> <p><span>Increase the value of&nbsp; <code>removeAbandonedTimeOut&nbsp;</code></span>in&nbsp;<strong>tomcat-resources.xml</strong>.</p> <h2>Affected Versions</h2> <p>This article applies to Appian&nbsp;19.1 and later.</p> <p>Last Reviewed: June 2020</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: database, application server, upgrade, infrastructure</div> https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments/revision/7Mon, 29 Jun 2020 21:29:40 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b5e56291-2097-494f-8f6a-61dc1975074aRebecca Jonashttps://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments#commentsRevision 7 posted to Appian Knowledge Base by Rebecca Jonas on 6/29/2020 9:29:40 PM<br /> <h2>Symptoms</h2> <p>Calls to the database from the app server fail after an upgrade or migration for an on-premise installation.&nbsp;<span>The following error can be seen in the application server log:</span></p> <pre class="code-java">ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit java.sql.SQLException: Connection has already been closed.</pre> <h2>Cause</h2> <p><span>Databases have a default timeout period after which idle connections are terminated, causing the a</span>pp server to be unable to make calls to the database.</p> <h2>Action</h2> <p><span>Increase the value of&nbsp; <code>removeAbandonedTimeOut&nbsp;</code></span>in&nbsp;<strong>tomcat-resources.xml</strong>.</p> <h2>Affected Versions</h2> <p>This article applies to Appian&nbsp;19.1 and later.</p> <p>Last Reviewed: June 2020</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: database, application server, upgrade, infrastructure</div> https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments/revision/6Mon, 29 Jun 2020 21:29:13 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b5e56291-2097-494f-8f6a-61dc1975074aRebecca Jonashttps://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments#commentsRevision 6 posted to Appian Knowledge Base by Rebecca Jonas on 6/29/2020 9:29:13 PM<br /> <h2>Symptoms</h2> <p>Calls to the database from the app server fail after an upgrade or migration for an on-premise installation.&nbsp;<span>The following error can be seen in the application server log:</span></p> <pre class="code-java">ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit java.sql.SQLException: Connection has already been closed.</pre> <h2>Cause</h2> <p><span>Databases have a default timeout period after which idle connections are terminated, causing the a</span>pp server to be unable to make calls to the database.</p> <h2>Action</h2> <p><span>Increase the value of&nbsp; <code>removeAbandonedTimeOut&nbsp;</code></span>in&nbsp;<strong>tomcat-resources.xml</strong>.</p> <h2>Affected Versions</h2> <p>This article applies to Appian&nbsp;19.1 and later.</p> <p>Last Reviewed: June 2020</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: database, application server</div> https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments/revision/5Mon, 29 Jun 2020 21:28:18 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b5e56291-2097-494f-8f6a-61dc1975074aRebecca Jonashttps://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments#commentsRevision 5 posted to Appian Knowledge Base by Rebecca Jonas on 6/29/2020 9:28:18 PM<br /> <h2>Symptoms</h2> <p>Calls to the database from the app server fail after an upgrade or migration for an on-premise installation.&nbsp;<span>The following error can be seen in the application server log:</span></p> <pre class="code-java">ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit java.sql.SQLException: Connection has already been closed.</pre> <h2>Cause</h2> <p><span>Databases have a default timeout period after which idle connections are terminated, causing the a</span>pp server to be unable to make calls to the database.</p> <h2>Action</h2> <p><span>Increase the value of&nbsp; <code>removeAbandonedTimeOut&nbsp;</code></span>in&nbsp;<strong>tomcat-resources.xml</strong>.</p> <h2>Affected Versions</h2> <p>This article applies to Appian&nbsp;19.1 and later.</p> <p>Last Reviewed: June 2020</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: database, application server</div> https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments/revision/4Mon, 29 Jun 2020 14:05:09 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b5e56291-2097-494f-8f6a-61dc1975074aKritesh Arorahttps://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments#commentsRevision 4 posted to Appian Knowledge Base by Kritesh Arora on 6/29/2020 2:05:09 PM<br /> <h2>Symptoms</h2> <p></p> <p>Calls to the database from app server fail after an upgrade or migration for an on-premise installation.&nbsp;<span>The following error can be seen in the application server log:</span></p> <pre class="code-java">ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit java.sql.SQLException: Connection has already been closed.<br /><br /></pre> <h2>Cause</h2> <p><span>&nbsp;Databases have a default timeout period after which it terminates idle connections, causing a</span>pp server to not be able to make calls to the database.</p> <h2>Action</h2> <p><span>Increase the value of&nbsp; <code>removeAbandonedTimeOut&nbsp;</code></span>in the&nbsp;<strong>tomcat-resources.xml</strong>.</p> <h2>Affected Versions</h2> <p>This article applies to Appian&nbsp;19.1 and later.</p> <p>Last Reviewed: June 2020</p> <div class="code panel"></div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: database, application server</div> https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments/revision/3Mon, 29 Jun 2020 14:02:14 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b5e56291-2097-494f-8f6a-61dc1975074aKritesh Arorahttps://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments#commentsRevision 3 posted to Appian Knowledge Base by Kritesh Arora on 6/29/2020 2:02:14 PM<br /> <h2>Symptoms</h2> <p></p> <p>Calls to the database from app server fail after an upgrade or migration.&nbsp;<span>The following error can be seen in the application server log:</span></p> <pre class="code-java">ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit java.sql.SQLException: Connection has already been closed.<br /><br /></pre> <h2>Cause</h2> <p><span>&nbsp;Databases have a default timeout period after which it terminates idle connections, causing a</span>pp server to not be able to make calls to the database.</p> <h2>Action</h2> <p><span>Increase the value of&nbsp; <code>removeAbandonedTimeOut&nbsp;</code></span>in the&nbsp;<strong>tomcat-resources.xml</strong>.</p> <h2>Affected Versions</h2> <p>This article applies to Appian&nbsp;19.1 and later.</p> <p>Last Reviewed: June 2020</p> <div class="code panel"></div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: database, application server</div> https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments/revision/2Mon, 29 Jun 2020 14:00:31 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b5e56291-2097-494f-8f6a-61dc1975074aKritesh Arorahttps://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments#commentsRevision 2 posted to Appian Knowledge Base by Kritesh Arora on 6/29/2020 2:00:31 PM<br /> <h2>Symptoms</h2> <p></p> <p>Calls to the database from app server fail after an upgrade or migration.&nbsp;<span>The following error can be seen in the application server log:</span></p> <pre class="code-java">ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit java.sql.SQLException: Connection has already been closed.<br /><br /></pre> <h2>Cause</h2> <p><span>&nbsp;Databases have a default timeout period after which it terminates idle connections, causing a</span>pp server to not be able to make calls to the database.</p> <h2>Action</h2> <p><span>Increase the value of&nbsp; removeAbandonedTimeOut&nbsp;</span>in the&nbsp;<strong>tomcat-resources.xml</strong>.</p> <h2>Affected Versions</h2> <p>This article applies to Appian&nbsp;19.1 and later.</p> <p>Last Reviewed: June 2020</p> <div class="code panel"></div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: database, application server</div> https://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments/revision/1Mon, 29 Jun 2020 13:59:39 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:b5e56291-2097-494f-8f6a-61dc1975074aKritesh Arorahttps://community.appian.com/support/w/kb/1891/kb-2143-database-calls-fail-with-connection-has-already-been-closed-for-self-managed-environments#commentsRevision 1 posted to Appian Knowledge Base by Kritesh Arora on 6/29/2020 1:59:39 PM<br /> <h2>Symptoms</h2> <p></p> <p>Calls to the database from app server fail after an upgrade or migration.&nbsp;<span>The following error can be seen in the application server log:</span></p> <pre class="code-java">ERROR org.hibernate.transaction.JDBCTransaction - Could not toggle autocommit java.sql.SQLException: Connection has already been closed.<br /><br /></pre> <h2>Cause</h2> <p><span>&nbsp;Databases have a default timeout period after which it terminates idle connections, causing a</span>pp server to not be able to make calls to the database.</p> <h2>Action</h2> <p><span>Increase the value of&nbsp; removeAbandonedTimeOut&nbsp;</span>in the&nbsp;<strong>tomcat-resources.xml</strong>.</p> <h2>Affected Versions</h2> <p>This article applies to Appian&nbsp;19.1 and later.</p> <p>Last Reviewed: June 2020</p> <div class="code panel"></div><div style="clear:both;"></div>