KB-1590 Database connection pool maxes out for Oracle data sources configured in the Admin Console

Parmida Borhani — Mon, 23 Jul 2018 03:19:54 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 7/23/2018 3:19:54 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

For an Oracle data source configured in the Admin Console, there is a notable increase in the number of used connections. Eventually, the connection pool maxes out, preventing any new queries from being executed against that data source.

Cause

There is an issue in the logger responsible for logging data source metrics for data sources defined through the Admin Console, resulting in a connection leak.

This issue has been resolved via AN-105369 in the following hotfixes/versions:

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Workaround

As the Appian user, open the appian_log4j.properties file located in <APPIAN_HOME>/ear/suite.ear/resources/.
Set the value of log4j.logger.com.appian.data-metrics.data_sources from INFO to FATAL. It should look like this: log4j.logger.com.appian.data-metrics.data_sources=FATAL, DATA_SOURCES_METRICS
Restart application server to clear out the inactive sessions.

Affected Versions

This article applies to Appian 17.4 and 18.1.

Last Reviewed: May 2018

Tags: database, infrastructure, oracle

KB-1590 Database connection pool maxes out for Oracle data sources configured in the Admin Console

Parmida Borhani — Thu, 31 May 2018 19:58:10 GMT

Revision 11 posted to Appian Knowledge Base by Parmida Borhani on 5/31/2018 7:58:10 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Cause

There is an issue in the logger responsible for logging data source metrics for data sources defined through the Admin Console, resulting in a connection leak.

This issue has been resolved via AN-105369 in the following hotfixes/versions:

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Workaround

As the Appian user, open the appian_log4j.properties file located in <APPIAN_HOME>/ear/suite.ear/resources/.
Set the value of log4j.logger.com.appian.data-metrics.data_sources from INFO to FATAL. It should look like this: log4j.logger.com.appian.data-metrics.data_sources=FATAL, DATA_SOURCES_METRICS
Restart application server to clear out the inactive sessions.

Affected Versions

This article applies to Appian 17.4 and 18.1.

Last Reviewed: May 2018

Tags: database, oracle

KB-1590 Database connection pool maxes out for Oracle data sources configured in the Admin Console

Parmida Borhani — Thu, 31 May 2018 19:57:50 GMT

Revision 10 posted to Appian Knowledge Base by Parmida Borhani on 5/31/2018 7:57:50 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Cause

There is an issue in the logger responsible for logging data source metrics for data sources defined through the Admin Console, resulting in a connection leak.

This issue has been resolved via AN-105369 in the following hotfixes/versions:

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Workaround

As the Appian user, open the appian_log4j.properties file located in <APPIAN_HOME>/ear/suite.ear/resources/.
Set the value of log4j.logger.com.appian.data-metrics.data_sources from INFO to FATAL. It should look like this: log4j.logger.com.appian.data-metrics.data_sources=FATAL, DATA_SOURCES_METRICS
Restart application server to clear out the inactive sessions.

Affected Versions

This article applies to Appian 17.4 and 18.1.

Last Reviewed: May 2018

Tags: database, oracle

KB-1590 Database connection pool maxes out for Oracle data sources configured in the Admin Console

Nick Vigilante — Thu, 31 May 2018 16:16:05 GMT

Revision 9 posted to Appian Knowledge Base by Nick Vigilante on 5/31/2018 4:16:05 PM

Symptoms

Cause

There is an issue in the logger responsible for logging data source metrics for data sources defined through the Admin Console, resulting in a connection leak.

This issue has been resolved via AN-105369 in the following hotfixes/versions:

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Workaround

As the Appian user, open the appian_log4j.properties file located in <APPIAN_HOME>/ear/suite.ear/resources/.
Set the value of log4j.logger.com.appian.data-metrics.data_sources from INFO to FATAL. It should look like this: log4j.logger.com.appian.data-metrics.data_sources=FATAL, DATA_SOURCES_METRICS
Restart application server to clear out the inactive sessions.

Affected Versions

This article applies to Appian 17.4 and 18.1.

Last Reviewed: May 2018

Tags: database, oracle

KB-XXXX: Database connection pool maxes out for Oracle data sources configured in the Admin Console

Nick Vigilante — Tue, 29 May 2018 15:24:44 GMT

Revision 8 posted to Appian Knowledge Base by Nick Vigilante on 5/29/2018 3:24:44 PM

Symptoms

Cause

There is an issue in the logger responsible for logging data source metrics for data sources defined through the Admin Console, resulting in a connection leak.

This issue has been resolved via AN-105369 in the following hotfixes/versions:

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Workaround

As the Appian user, open the appian_log4j.properties file located in <APPIAN_HOME>/ear/suite.ear/resources/.
Set the value of log4j.logger.com.appian.data-metrics.data_sources from INFO to FATAL. It should look like this: log4j.logger.com.appian.data-metrics.data_sources=FATAL, DATA_SOURCES_METRICS
Restart application server to clear out the inactive sessions.

Affected Versions

This article applies to Appian 17.4 and 18.1.

Last Reviewed: May 2018

Tags: database, oracle

KB-XXXX: Database connection pool maxes out for Oracle data sources configured in the Admin Console

Stephen Okala — Tue, 29 May 2018 15:22:59 GMT

Revision 7 posted to Appian Knowledge Base by Stephen Okala on 5/29/2018 3:22:59 PM

Symptoms

Cause

There is an issue in the logger responsible for logging data source metrics for data sources defined through the Admin Console, resulting in a connection leak.

This issue has been resolved via AN-105369 in the following hotfixes/versions:

17.4-HF G: (https://docs.appian.com/suite/help/17.4/Hotfixes.html)
18.1-HF C: (https://docs.appian.com/suite/help/18.1/Hotfixes.html)

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Workaround

As the Appian user, open the appian_log4j.properties file located in <APPIAN_HOME>/ear/suite.ear/resources/.
Set the value of log4j.logger.com.appian.data-metrics.data_sources from INFO to FATAL. It should look like this: log4j.logger.com.appian.data-metrics.data_sources=FATAL, DATA_SOURCES_METRICS
Restart application server to clear out the inactive sessions.

Affected Versions

This article applies to Appian 17.4 and 18.1.

Last Reviewed: May 2018

Tags: database, oracle

KB-XXXX: Database connection pool maxes out for Oracle data sources configured in the Admin Console

Nick Vigilante — Tue, 29 May 2018 15:18:30 GMT

Revision 6 posted to Appian Knowledge Base by Nick Vigilante on 5/29/2018 3:18:30 PM

Symptoms

Cause

There is an issue in the logger responsible for logging data source metrics for data sources defined through the Admin Console, resulting in a connection leak.

This issue has been resolved via AN-105369 in the following hotfixes/versions:

List hotfixes here and link to each hotfix page

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Workaround

As the Appian user, open the appian_log4j.properties file located in <APPIAN_HOME>/ear/suite.ear/resources/.
Set the value of log4j.logger.com.appian.data-metrics.data_sources from INFO to FATAL. It should look like this: log4j.logger.com.appian.data-metrics.data_sources=FATAL, DATA_SOURCES_METRICS
Restart application server to clear out the inactive sessions.

Affected Versions

This article applies to Appian 17.4 and 18.1.

Last Reviewed: Month yyyy

Tags: database, oracle

KB-XXXX: Database connections issue in 17.4 and 18.1

Nick Vigilante — Tue, 29 May 2018 15:17:53 GMT

Revision 5 posted to Appian Knowledge Base by Nick Vigilante on 5/29/2018 3:17:53 PM

Symptoms

Cause

There is an issue in the logger responsible for logging data source metrics for data sources defined through the Admin Console, resulting in a connection leak.

This issue has been resolved via AN-105369 in the following hotfixes/versions:

List hotfixes here and link to each hotfix page

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Workaround

As the Appian user, open the appian_log4j.properties file located in <APPIAN_HOME>/ear/suite.ear/resources/.
Set the value of log4j.logger.com.appian.data-metrics.data_sources from INFO to FATAL. It should look like this: log4j.logger.com.appian.data-metrics.data_sources=FATAL, DATA_SOURCES_METRICS
Restart application server to clear out the inactive sessions.

Affected Versions

This article applies to Appian 17.4 and 18.1.

Last Reviewed: Month yyyy

Tags: database, oracle

KB-XXXX: Database connections issue in 17.4 and 18.1

Stephen Okala — Wed, 23 May 2018 10:29:54 GMT

Revision 4 posted to Appian Knowledge Base by Stephen Okala on 5/23/2018 10:29:54 AM

Symptoms

The number of secondary data source connections, configured in the Admin Console, pointing to an Oracle database would climb up by a factor of five. This will cause a high number of inactive connections to the database indicating a high load from the application.

Cause

There was a data source connection leak in the code that logs data source metrics for data sources defined through Admin Console. This issue has been resolved via AN-105369 in the following hotfixes/versions:

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Workaround

Make sure the user has read/write/execute access on the server.
Open the log4j.properties file located in <APPIAN_HOME>/ear/suite.ear/resources/appian_log4j.properties
Set the value of log4j.logger.com.appian.data-metrics.data_sources from INFO to FATAL. It should look like this: log4j.logger.com.appian.data-metrics.data_sources=FATAL, DATA_SOURCES_METRICS
Restart application server to clear out the inactive sessions

Affected Versions

This article applies to Appian 17.4 and later.

Tags: database, oracle

KB-XXXX: Database connections issue in 17.4 and 18.1

Stephen Okala — Wed, 09 May 2018 20:11:44 GMT

Revision 1 posted to Appian Knowledge Base by Stephen Okala on 5/9/2018 8:11:44 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian 17.4 and 18.1 installation or upgrade to the latest version of Appian.

Symptoms

The number of secondary data source connections, configured in the admin console, pointing to an Oracle database would climb up by a factor of five. This will cause a high number of inactive connections to the database indicating a high load from the application.

Cause

There was a data source connection leak in the code that logs data source metrics for data sources defined through admin console.

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Workaround

Make sure the user has read/write/execute access on the server.
Open the log4j.properties file located in <APPIAN_HOME>/ear/suite.ear/resources/appian_log4j.properties
Set the value of log4j.logger.com.appian.data-metrics.data_sources from INFO to FATAL. It should look like this: log4j.logger.com.appian.data-metrics.data_sources=FATAL, DATA_SOURCES_METRICS
Restart application server to clear out the inactive sessions

Affected Versions

This article applies to Appian 17.4 and later.

Tags: database, oracle

KB-XXXX: Database connections issue in 17.4 and 18.1

Stephen Okala — Wed, 09 May 2018 16:16:40 GMT

Revision 3 posted to Appian Knowledge Base by Stephen Okala on 5/9/2018 4:16:40 PM

Symptoms

Cause

There was a data source connection leak in the code that logs data source metrics for data sources defined through admin console.

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Workaround

Make sure the user has read/write/execute access on the server.
Open the log4j.properties file located in <APPIAN_HOME>/ear/suite.ear/resources/appian_log4j.properties
Set the value of log4j.logger.com.appian.data-metrics.data_sources from INFO to FATAL. It should look like this: log4j.logger.com.appian.data-metrics.data_sources=FATAL, DATA_SOURCES_METRICS
Restart application server to clear out the inactive sessions

Affected Versions

This article applies to Appian 17.4 and later.

Tags: database, oracle

KB-XXXX: Database connections issue in 17.4 and 18.1

Stephen Okala — Wed, 09 May 2018 16:14:31 GMT

Revision 2 posted to Appian Knowledge Base by Stephen Okala on 5/9/2018 4:14:31 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian 17.4 and 18.1 installation or upgrade to the latest version of Appian.

Symptoms

Cause

There was a data source connection leak in the code that logs data source metrics for data sources defined through admin console.

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Workaround

Make sure the user has read/write/execute access on the server.
Open the log4j.properties file located in <APPIAN_HOME>/ear/suite.ear/resources/appian_log4j.properties
Set the value of log4j.logger.com.appian.data-metrics.data_sources from INFO to FATAL. It should look like this: log4j.logger.com.appian.data-metrics.data_sources=FATAL, DATA_SOURCES_METRICS
Restart application server to clear out the inactive sessions

Affected Versions

This article applies to Appian 17.4 and later.

Tags: database, oracle