KB-2184 "java.sql.SQLException: Unable to obtain a connection within configured timeout" observed in application server log

Parmida Borhani — Thu, 06 May 2021 22:34:54 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 5/6/2021 10:34:54 PM

Symptoms

The following exception appears in the tomcat-stdOut.log file:

Caused by: java.sql.SQLException: Unable to obtain a connection within configured timeout

In cases where this exception is encountered regularly, application features that interact with databases may experience degraded performance. This can manifest in a number of ways, ranging from user-facing application slowness to frequently failing process model execution.

Cause

The application server was unable to establish a connection to the business database within the default 10 second timeout. The timeout is in place to prevent the application from locking up if a large number of threads are blocked waiting for a database connection to initialize. In many cases, this error message is a symptom of an unreliable network configuration between the web server and the database, rather than an issue localized to either of those components.

Action

Work with your database administrators, network operations team, and/or Appian Support to verify the reliability of the network connection between the application server and the database instance.

Workaround

In cases when the network conditions or database responsiveness cannot be improved, increase or disable the connection timeout properties.

DISCLAIMER: These properties only affect the way the application server reacts to slow connection attempts. Without addressing the underlying issues, modifications to these values may degrade application performance.

Self-Managed

Modify or add the following properties to the custom.properties file:
- conf.data.datasources.internal.CONNECTION_TIMEOUT_MS=<time in milliseconds>
- conf.data.datasources.internal.connectionTimeout.enabled=false
Restart the application server.

Notes:

There is no "correct" value for the CONNECTION_TIMEOUT_MS property. Choose a value based on tolerance for latency. The default value is 10000.
If the connectionTimeout.enabled property is set to false, the timeout above is ignored. The default value is true.

Cloud

Open a case with Appian Support to request a change to these values. A site restart will be required to apply the configuration changes.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: May 2021

Tags: database, application server, timeout, network, connection

DRAFT SP-6217: "java.sql.SQLException: Unable to obtain a connection within configured timeout"

David Loewy — Thu, 06 May 2021 20:37:23 GMT

Revision 5 posted to Appian Knowledge Base by David Loewy on 5/6/2021 8:37:23 PM

Symptoms

The following exception appears in the tomcat-stdOut.log file:

Caused by: java.sql.SQLException: Unable to obtain a connection within configured timeout

Cause

Action

Work with your database administrators, network operations team, and/or Appian Support to verify the reliability of the network connection between the application server and the database instance.

Workaround

In cases when the network conditions or database responsiveness cannot be improved, increase or disable the connection timeout properties.

Self-Managed

Modify or add the following properties to the custom.properties file:
- conf.data.datasources.internal.CONNECTION_TIMEOUT_MS=<time in milliseconds>
- conf.data.datasources.internal.connectionTimeout.enabled=false
Restart the application server.

Notes:

There is no "correct" value for the CONNECTION_TIMEOUT_MS property. Choose a value based on tolerance for latency. The default value is 10000.
If the connectionTimeout.enabled property is set to false, the timeout above is ignored. The default value is true.

Cloud

Open a case with Appian Support to request a change to these values. A site restart will be required to apply the configuration changes.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: May 2021

Tags: database, application server

DRAFT SP-6217: "java.sql.SQLException: Unable to obtain a connection within configured timeout"

Parmida Borhani — Thu, 06 May 2021 00:00:06 GMT

Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 5/6/2021 12:00:06 AM

Symptoms

The following exception appears in the tomcat-stdOut.log file:

Caused by: java.sql.SQLException: Unable to obtain a connection within configured timeout

Cause

Action

Work with your database administrators, network operations team, and/or Appian Support to verify the reliability of the network connection between the application server and the database instance.

Workaround

In cases when the network conditions or database responsiveness cannot be improved, increase or disable the connection timeout properties.

Self-Managed

Modify or add the following properties to the custom.properties file:
- conf.data.datasources.internal.CONNECTION_TIMEOUT_MS=<time in milliseconds>
- conf.data.datasources.internal.connectionTimeout.enabled=false
Restart the application server.

Notes:

There is no "correct" value for the CONNECTION_TIMEOUT_MS property. Choose a value based on tolerance for latency. The default value is 10000.
If the connectionTimeout.enabled property is set to false, the timeout above is ignored. The default value is true.

Cloud

Open a case with Appian Support to request a change to these values. A site restart will be required to apply the configuration changes.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: May 2021

Tags: database, application server

DRAFT SP-6217: "java.sql.SQLException: Unable to obtain a connection within configured timeout"

Parmida Borhani — Wed, 05 May 2021 23:59:40 GMT

Revision 3 posted to Appian Knowledge Base by Parmida Borhani on 5/5/2021 11:59:40 PM

Symptoms

The following exception appears in the tomcat-stdOut.log file:

Caused by: java.sql.SQLException: Unable to obtain a connection within configured timeout

Cause

Action

Work with your database administrators, network operations team, and/or Appian Support to verify the reliability of the network connection between the application server and the database instance.

Workaround

In cases when the network conditions or database responsiveness cannot be improved, increase or disable the connection timeout properties. DISCLAIMER: These properties only affect the way the application server reacts to slow connection attempts. Without addressing the underlying issues, modifications to these values may degrade application performance.

Self-Managed

Modify or add the following properties to the custom.properties file:
- conf.data.datasources.internal.CONNECTION_TIMEOUT_MS=<time in milliseconds>
- conf.data.datasources.internal.connectionTimeout.enabled=false
Restart the application server.

Notes:

There is no "correct" value for the CONNECTION_TIMEOUT_MS property. Choose a value based on tolerance for latency. The default value is 10000.
If the connectionTimeout.enabled property is set to false, the timeout above is ignored. The default value is true.

Cloud

Open a case with Appian Support to request a change to these values. A site restart will be required to apply the configuration changes.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: May 2021

Tags: database, application server

DRAFT SP-6217: "java.sql.SQLException: Unable to obtain a connection within configured timeout"

David Loewy — Wed, 05 May 2021 16:04:50 GMT

Revision 2 posted to Appian Knowledge Base by David Loewy on 5/5/2021 4:04:50 PM

Symptoms

The following exception appears in the tomcat-stdOut.log file:

Caused by: java.sql.SQLException: Unable to obtain a connection within configured timeout

Cause

By default, the application server applies a 10 second timeout when attempting to establish a connection to a business database. Without this timeout, the application runs the risk of locking up if a large number of threads get blocked waiting for a database connection to initialize.

In many cases, this error message is a symptom of an unreliable network configuration between the web server and the database, rather than an issue localized to either of those components.

Action

Option 1

Work with your database administrators, network operations team, and/or Appian Cloud Support to verify the reliability of the network connection between the application server and the database instance.

Option 2

In cases when the network conditions or database responsiveness cannot be improved, extend or disable the connection timeout. Modify or add the following properties to the custom.properties file, then restart the application server.

Note: These properties only affect the way the application server reacts to slow connection attempts. Without addressing the underlying issues per Option 1, modifications to these values may degrade application server performance.

# There is no "correct" value for this property. Choose a value based on tolerance for latency.
# Default: 10000
conf.data.datasources.internal.CONNECTION_TIMEOUT_MS=<time in milliseconds>

# If this property is set to `false`, the timeout above is ignored.
# Default: true
conf.data.datasources.internal.connectionTimeout.enabled=false

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: May 2021

Tags: database, application server

DRAFT SP-6217: "java.sql.SQLException: Unable to obtain a connection within configured timeout"

David Loewy — Tue, 04 May 2021 15:34:33 GMT

Revision 1 posted to Appian Knowledge Base by David Loewy on 5/4/2021 3:34:33 PM

Symptoms

The following exception appears in the tomcat-stdOut.log file:

Caused by: java.sql.SQLException: Unable to obtain a connection within configured timeout

Cause

In many cases, this error message is a symptom of an unreliable network configuration between the web server and the database, rather than an issue localized to either of those components.

Action

Option 1

Option 2

# Default: 10000
conf.data.datasources.internal.CONNECTION_TIMEOUT_MS=30000

# Default: true
conf.data.datasources.internal.connectionTimeout.enabled=false

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: May 2021

Tags: database, application server