KB-1681 Unable to retrieve data due to query timeout

Elly Meng — Wed, 11 May 2022 16:25:15 GMT

Current Revision posted to Appian Knowledge Base by Elly Meng on 5/11/2022 4:25:15 PM

Symptoms

A query rule fails to run and one of the following errors is seen in the application server log:

Expression evaluation error in rule '<rule name>' (called by rules '<rule name 1>' > '<rule name 2>') at function a!queryEntity: An error occurred while retrieving the data. (APNX-1-4198-000)

Expression evaluation error in rule '<rule name>' at function 'queryruleexec': Error evaluating function 'queryruleexec' : Unexpected error executing query (type: [<CDT name>], query: [<rule name>], order by: [[]], filters:[null])

with one of the following "caused by" clauses:

Caused by: java.sql.SQLTimeoutException: (conn=<connection id>) Query execution was interrupted (max_statement_time exceeded)

Caused by: com.mysql.jdbc.exceptions.MySQLTimeoutException: Statement cancelled due to timeout or client request

Caused by: org.hibernate.exception.GenericJDBCException: could not execute query

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The query has timed out.

Cause

These errors indicate that the query reached the query timeout threshold, causing it to time out. This threshold is set to 10 seconds for Appian Cloud environments. For more information about this timeout threshold, see our documentation on Query Rule Limits.

Action

Review the 'Execute Time (ms)' column of the perf_monitor_rdbms_slow.csv log located in <APPIAN_HOME>/logs/perflogs to confirm if the failed query exceeded the configured timeout value.

The query should be optimized so that it can be completed within the timeout. See: Database Performance Best Practices and An Introduction to Query Optimization.

Note: increasing the timeout threshold may impact system performance and stability, and is not configurable for Appian Cloud.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: May 2022

Tags: database, query rules, Performance, infrastructure, Cloud

KB-1681 Unable to retrieve data due to query timeout

Parmida Borhani — Mon, 10 Sep 2018 21:04:43 GMT

Revision 13 posted to Appian Knowledge Base by Parmida Borhani on 9/10/2018 9:04:43 PM

Symptoms

A query rule fails to run, and one of the following error(s) is seen in the application server log:

Expression evaluation error in rule '<rule name>' (called by rules '<rule name 1>' > '<rule name 2>') at function a!queryEntity: An error occurred while retrieving the data. (APNX-1-4198-000)

Expression evaluation error in rule '<rule name>' at function 'queryruleexec': Error evaluating function 'queryruleexec' : Unexpected error executing query (type: [<CDT name>], query: [<rule name>], order by: [[]], filters:[null])

with one of the following caused by clauses:

Caused by: com.mysql.jdbc.exceptions.MySQLTimeoutException: Statement cancelled due to timeout or client request

Caused by: org.hibernate.exception.GenericJDBCException: could not execute query

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The query has timed out.

Cause

These errors indicate that the query has reached the query timeout threshold which has caused the query to time out. For more information on the timeout threshold, see: Query Rule Limits. For Appian Cloud environments, this threshold is set at 10 seconds.

Action

Review the 'Execute Time (ms)' column of the perf_monitor_rdbms_slow.csv log located in <APPIAN_HOME>/logs/perflogs to confirm if the failed query has exceeded the configured timeout value.

The query should be optimized so that it can be completed within the timeout. Note that increasing the timeout threshold may impact the system performance and stability. The query timeout value is not configurable in Appian Cloud.

Also see: Database Performance Best Practices and An Introduction to Query Optimization.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2018

Tags: database, query rules, Performance, infrastructure, Cloud

KB-1681 Unable to retrieve data due to query timeout

Parmida Borhani — Mon, 10 Sep 2018 21:04:09 GMT

Revision 12 posted to Appian Knowledge Base by Parmida Borhani on 9/10/2018 9:04:09 PM

Symptoms

A query rule fails to run, and one of the following error(s) is seen in the application server log:

Expression evaluation error in rule '<rule name>' (called by rules '<rule name 1>' > '<rule name 2>') at function a!queryEntity: An error occurred while retrieving the data. (APNX-1-4198-000)

Expression evaluation error in rule '<rule name>' at function 'queryruleexec': Error evaluating function 'queryruleexec' : Unexpected error executing query (type: [<CDT name>], query: [<rule name>], order by: [[]], filters:[null])

with the following caused by:

Caused by: com.mysql.jdbc.exceptions.MySQLTimeoutException: Statement cancelled due to timeout or client request

Caused by: org.hibernate.exception.GenericJDBCException: could not execute query

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The query has timed out.

Cause

Action

Review the 'Execute Time (ms)' column of the perf_monitor_rdbms_slow.csv log located in <APPIAN_HOME>/logs/perflogs to confirm if the failed query has exceeded the configured timeout value.

Also see: Database Performance Best Practices and An Introduction to Query Optimization.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2018

Tags: database, query rules, Performance, infrastructure, Cloud

KB-1681 Unable to retrieve data due to query timeout

Parmida Borhani — Mon, 10 Sep 2018 20:58:41 GMT

Revision 11 posted to Appian Knowledge Base by Parmida Borhani on 9/10/2018 8:58:41 PM

Symptoms

A query rule fails to run, and one of the following error(s) is seen in the application server log:

Expression evaluation error in rule '<rule name>' (called by rules '<rule name 1>' > '<rule name 2>') at function a!queryEntity: An error occurred while retrieving the data. (APNX-1-4198-000)

Expression evaluation error in rule '<rule name>' at function 'queryruleexec': Error evaluating function 'queryruleexec' : Unexpected error executing query (type: [<CDT name>], query: [<rule name>], order by: [[]], filters:[null])

with the following caused by:

Caused by: com.mysql.jdbc.exceptions.MySQLTimeoutException: Statement cancelled due to timeout or client request

Cause

Action

Review the 'Execute Time (ms)' column of the perf_monitor_rdbms_slow.csv log located in <APPIAN_HOME>/logs/perflogs to confirm if the failed query has exceeded the configured timeout value.

Also see: Database Performance Best Practices and An Introduction to Query Optimization.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2018

Tags: database, query rules, Performance, infrastructure, Cloud

KB-1681 MySQLTimeoutException: Statement cancelled due to timeout or client request

Parmida Borhani — Thu, 30 Aug 2018 02:56:43 GMT

Revision 10 posted to Appian Knowledge Base by Parmida Borhani on 8/30/2018 2:56:43 AM

Symptoms

A query rule fails to run, and one of the following error(s) is seen in the application server log:

Expression evaluation error in rule '<rule name>' (called by rules '<rule name 1>' > '<rule name 2>') at function a!queryEntity: An error occurred while retrieving the data. (APNX-1-4198-000)

Expression evaluation error in rule '<rule name>' at function 'queryruleexec': Error evaluating function 'queryruleexec' : Unexpected error executing query (type: [<CDT name>], query: [<rule name>], order by: [[]], filters:[null])

with the following caused by:

Caused by: com.mysql.jdbc.exceptions.MySQLTimeoutException: Statement cancelled due to timeout or client request

Cause

The MySQLTimeoutException indicates that the query has reached the query timeout threshold which has caused the query to time out. For more information on the timeout threshold, see: Query Rule Limits. For Appian Cloud environments, this threshold is set at 10 seconds.

Action

Review the 'Execute Time (ms)' column of the perf_monitor_rdbms_slow.csv log located in <APPIAN_HOME>/logs/perflogs to confirm if the failed query has exceeded the configured timeout value.

Also see: Database Performance Best Practices and An Introduction to Query Optimization.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: database, query rules, Performance, infrastructure, Cloud

[DRAFT] KB-XXXX MySQLTimeoutException: Statement cancelled due to timeout or client request

Parmida Borhani — Wed, 29 Aug 2018 22:56:05 GMT

Revision 9 posted to Appian Knowledge Base by Parmida Borhani on 8/29/2018 10:56:05 PM

Symptoms

A query rule fails to run, and one of the following error(s) is seen in the application server log:

Expression evaluation error in rule '<rule name>' (called by rules '<rule name 1>' > '<rule name 2>') at function a!queryEntity: An error occurred while retrieving the data. (APNX-1-4198-000)

Expression evaluation error in rule '<rule name>' at function 'queryruleexec': Error evaluating function 'queryruleexec' : Unexpected error executing query (type: [<CDT name>], query: [<rule name>], order by: [[]], filters:[null])

with the following caused by:

Caused by: com.mysql.jdbc.exceptions.MySQLTimeoutException: Statement cancelled due to timeout or client request

Cause

Action

Review the 'Execute Time (ms)' column of the perf_monitor_rdbms_slow.csv log located in <APPIAN_HOME>/logs/perflogs to confirm if the failed query has exceeded the configured timeout value.

Also see: Database Performance Best Practices and An Introduction to Query Optimization.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: database, query rules, Performance, infrastructure, Cloud

[DRAFT] KB-XXXX MySQLTimeoutException: Statement cancelled due to timeout or client request

Parmida Borhani — Wed, 29 Aug 2018 22:52:23 GMT

Revision 8 posted to Appian Knowledge Base by Parmida Borhani on 8/29/2018 10:52:23 PM

Symptoms

A query rule fails to run, and one of the following error(s) is seen in the application server log:

Expression evaluation error in rule '<rule name>' (called by rules '<rule name 1>' > '<rule name 2>') at function a!queryEntity: An error occurred while retrieving the data. (APNX-1-4198-000)

Expression evaluation error in rule '<rule name>' at function 'queryruleexec': Error evaluating function 'queryruleexec' : Unexpected error executing query (type: [<CDT name>], query: [<rule name>], order by: [[]], filters:[null])

with the following caused by:

Caused by: com.mysql.jdbc.exceptions.MySQLTimeoutException: Statement cancelled due to timeout or client request

Cause

Action

Review the 'Execute Time (ms)' column of the perf_monitor_rdbms_slow.csv log located in <APPIAN_HOME>/logs/perflogs to confirm if the failed query has exceeded the configured timeout value.

Also see: Database Performance Best Practices and An Introduction to Query Optimization.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: database, query rules, Performance, infrastructure, Cloud

[DRAFT] KB-XXXX MySQLTimeoutException: Statement cancelled due to timeout or client request

Parmida Borhani — Wed, 29 Aug 2018 22:48:50 GMT

Revision 7 posted to Appian Knowledge Base by Parmida Borhani on 8/29/2018 10:48:50 PM

Symptoms

A query rule fails to run, and one of the following error(s) is seen in the application server log:

Expression evaluation error in rule '<rule name>' (called by rules '<rule name 1>' > '<rule name 2>') at function a!queryEntity: An error occurred while retrieving the data. (APNX-1-4198-000)

Expression evaluation error in rule '<rule name>' at function 'queryruleexec': Error evaluating function 'queryruleexec' : Unexpected error executing query (type: [<CDT name>], query: [<rule name>], order by: [[]], filters:[null])

with the following caused by:

Caused by: com.mysql.jdbc.exceptions.MySQLTimeoutException: Statement cancelled due to timeout or client request

Cause

Action

Review the 'Execute Time (ms)' column of the perf_monitor_rdbms_slow.csv log located in <APPIAN_HOME>/logs/perflogs to confirm if the failed query has exceeded the configured timeout value.

Also see: Database Performance Best Practices and An Introduction to Query Optimization.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: database, query rules, Performance, infrastructure, Cloud

[DRAFT] KB-XXXX MySQLTimeoutException: Statement cancelled due to timeout or client request

Tom Ryan — Wed, 29 Aug 2018 19:57:00 GMT

Revision 6 posted to Appian Knowledge Base by Tom Ryan on 8/29/2018 7:57:00 PM

Symptoms

A query rule fails to run, and the following error is seen in the application server log:

Expression evaluation error in rule '<rule name>' at function 'queryruleexec': Error evaluating function 'queryruleexec' : Unexpected error executing query (type: [<CDT name>], query: [<rule name>], order by: [[]], filters:[null])
.
.
.
Caused by: com.mysql.jdbc.exceptions.MySQLTimeoutException: Statement cancelled due to timeout or client request

Cause

Action

Review the 'Execute Time (ms)' column of the perf_monitor_rdbms_slow.csv log located in <APPIAN_HOME>/logs/perflogs to confirm if the failed query has exceeded the configured timeout value.

Also see: Database Performance Best Practices and An Introduction to Query Optimization.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: database, query rules, Performance, infrastructure, Cloud

[DRAFT] KB-XXXX MySQLTimeoutException: Statement cancelled due to timeout or client request

Tom Ryan — Wed, 29 Aug 2018 19:55:34 GMT

Revision 5 posted to Appian Knowledge Base by Tom Ryan on 8/29/2018 7:55:34 PM

Symptoms

A query rule fails to run, and the following error is seen in the application server log:

Expression evaluation error in rule '<rule name>' at function 'queryruleexec': Error evaluating function 'queryruleexec' : Unexpected error executing query (type: [<CDT name>], query: [<rule name>], order by: [[]], filters:[null])
.
.
.
Caused by: com.mysql.jdbc.exceptions.MySQLTimeoutException: Statement cancelled due to timeout or client request

Cause

Action

Review the 'Execute Time (ms)' column of the perf_monitor_rdbms_slow.csv log located in <APPIAN_HOME>/logs/perflogs to confirm if the failed query has exceeded the configured timeout value.

Also see: Database Performance Best Practices and An Introduction to Query Optimization.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: database, query rules, Performance, infrastructure, Cloud

[DRAFT] KB-XXXX MySQLTimeoutException: Statement cancelled due to timeout or client request

Tom Ryan — Wed, 29 Aug 2018 19:44:55 GMT

Revision 4 posted to Appian Knowledge Base by Tom Ryan on 8/29/2018 7:44:55 PM

Symptoms

A query rule fails to run, and the following error is seen in the application server log:

Expression evaluation error in rule '<rule name>' at function 'queryruleexec': Error evaluating function 'queryruleexec' : Unexpected error executing query (type: [<CDT name>], query: [<rule name>], order by: [[]], filters:[null])
.
.
.
Caused by: com.mysql.jdbc.exceptions.MySQLTimeoutException: Statement cancelled due to timeout or client request

Cause

The MySQLTimeoutException suggests that the query has reached the ten second query timeout in Appian Cloud. In on-premise environments of Appian, the timeout value may differ based on the implementation.

Action

Review the 'Execute Time (ms)' column of the perf_monitor_rdbms_slow.csv log located in <APPIAN_HOME>/logs/perflogs to confirm if the failed query has exceeded the configured timeout value.

The query timeout value is not configurable in Appian Cloud. Instead, the query should be optimized so that the data can be returned within ten seconds.

Also see: Database Performance Best Practices and An Introduction to Query Optimization.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: database, query rules, Performance, infrastructure, Cloud

[DRAFT] KB-XXXX MySQLTimeoutException: Statement cancelled due to timeout or client request

Parmida Borhani — Wed, 29 Aug 2018 01:21:15 GMT

Revision 1 posted to Appian Knowledge Base by Parmida Borhani on 8/29/2018 1:21:15 AM

Symptoms

A query rule fails to run, and the following error is seen in the application server log:

Expression evaluation error in rule '<rule name>' at function 'queryruleexec': Error evaluating function 'queryruleexec' : Unexpected error executing query (type: [<CDT name>], query: [<rule name>], order by: [[]], filters:[null])
.
.
.
Caused by: com.mysql.jdbc.exceptions.MySQLTimeoutException: Statement cancelled due to timeout or client request

Cause

Action

Review the 'Execute Time (ms)' column of the perf_monitor_rdbms_slow.csv log located in <APPIAN_HOME>/logs/perflogs to confirm if the failed query has exceeded the configured timeout value.

The query timeout value cannot be modified in Appian Cloud. Instead, the query should be optimized so that the data can be returned within ten seconds.

Also see: Database Performance Best Practices and An Introduction to Query Optimization.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: database, query rules, Performance

[DRAFT] KB-XXXX MySQLTimeoutException: Statement cancelled due to timeout or client request

Parmida Borhani — Tue, 28 Aug 2018 21:24:12 GMT

Revision 3 posted to Appian Knowledge Base by Parmida Borhani on 8/28/2018 9:24:12 PM

Symptoms

A query rule fails to run, and the following error is seen in the application server log:

Expression evaluation error in rule '<rule name>' at function 'queryruleexec': Error evaluating function 'queryruleexec' : Unexpected error executing query (type: [<CDT name>], query: [<rule name>], order by: [[]], filters:[null])
.
.
.
Caused by: com.mysql.jdbc.exceptions.MySQLTimeoutException: Statement cancelled due to timeout or client request

Cause

Action

Review the 'Execute Time (ms)' column of the perf_monitor_rdbms_slow.csv log located in <APPIAN_HOME>/logs/perflogs to confirm if the failed query has exceeded the configured timeout value.

The query timeout value cannot be modified in Appian Cloud. Instead, the query should be optimized so that the data can be returned within ten seconds.

Also see: Database Performance Best Practices and An Introduction to Query Optimization.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: database, query rules, Performance, infrastructure, Cloud

[DRAFT] KB-XXXX MySQLTimeoutException: Statement cancelled due to timeout or client request

Parmida Borhani — Tue, 28 Aug 2018 21:23:57 GMT

Revision 2 posted to Appian Knowledge Base by Parmida Borhani on 8/28/2018 9:23:57 PM

Symptoms

A query rule fails to run, and the following error is seen in the application server log:

Expression evaluation error in rule '<rule name>' at function 'queryruleexec': Error evaluating function 'queryruleexec' : Unexpected error executing query (type: [<CDT name>], query: [<rule name>], order by: [[]], filters:[null])
.
.
.
Caused by: com.mysql.jdbc.exceptions.MySQLTimeoutException: Statement cancelled due to timeout or client request

Cause

Action

Review the 'Execute Time (ms)' column of the perf_monitor_rdbms_slow.csv log located in <APPIAN_HOME>/logs/perflogs to confirm if the failed query has exceeded the configured timeout value.

The query timeout value cannot be modified in Appian Cloud. Instead, the query should be optimized so that the data can be returned within ten seconds.

Also see: Database Performance Best Practices and An Introduction to Query Optimization.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: database, query rules, Performance