KB-1661 Daily performance degradation and long 'getAppianObject' calls to the content engine caused by the data collection for the Expression Rule Test Cases data metrics log

Jordan Horwat — Mon, 26 Nov 2018 16:42:49 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 11/26/2018 4:42:49 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

Users experience short bursts of unresponsiveness and failed processes every day around the same time.
There are long getAppianObject calls to the content engine. These calls can be viewed in the db_CO1*.log file located at <APPIAN_HOME>/logs directory.
The times of the long getAppianObject calls in the db_CO1*.log file correspond with the timestamps in the expression_rule_test_cases.csv file located at <APPIAN_HOME>/logs/data-metrics directory.

Cause

This issue has been addressed via AN-104637 in the following hotfixes/versions:

Action

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

Workaround

The following workaround can be used as a temporary measure until the hotfix or upgrade can be applied.

Edit the appian_log4j.properties file located at <APPIAN_HOME>/ear/suite.ear/resources, changing the following logger from:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=INFO

to:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=OFF

Affected Versions

This article applies to all versions of Appian from Appian 17.2 to Appian 18.1.

Last Reviewed: August 2018

Tags: logging, known issues, administration, engines, fixed issues, Performance, infrastructure

KB-1661 Daily performance degradation and long 'getAppianObject' calls to the content engine caused by the data collection for the Expression Rule Test Cases data metrics log

Jordan Horwat — Fri, 24 Aug 2018 16:39:55 GMT

Revision 13 posted to Appian Knowledge Base by Jordan Horwat on 8/24/2018 4:39:55 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

Users experience short bursts of unresponsiveness and failed processes every day around the same time.
There are long getAppianObject calls to the content engine. These calls can be viewed in the db_CO1*.log file located at <APPIAN_HOME>/logs directory.
The times of the long getAppianObject calls in the db_CO1*.log file correspond with the timestamps in the expression_rule_test_cases.csv file located at <APPIAN_HOME>/logs/data-metrics directory.

Cause

This issue has been addressed via AN-104637 in the following hotfixes/versions:

Action

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

Workaround

The following workaround can be used as a temporary measure until the hotfix or upgrade can be applied.

Edit the appian_log4j.properties file located at <APPIAN_HOME>/ear/suite.ear/resources, changing the following logger from:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=INFO

to:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=OFF

Affected Versions

This article applies to Appian 17.2 and later.

Last Reviewed: August 2018

Tags: logging, known issues, administration, engines, fixed issues, Performance, infrastructure

KB-1661 Daily performance degradation and long 'getAppianObject' calls to the content engine caused by the data collection for the Expression Rule Test Cases data metrics log

Jordan Horwat — Wed, 22 Aug 2018 13:19:00 GMT

Revision 12 posted to Appian Knowledge Base by Jordan Horwat on 8/22/2018 1:19:00 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

Users experience short bursts of unresponsiveness and failed processes every day around the same time.
There are long getAppianObject calls to the content engine. These calls can be viewed in the db_CO1*.log file located at <APPIAN_HOME>/logs directory.
The times of the long getAppianObject calls in the db_CO1*.log file correspond with the timestamps in the expression_rule_test_cases.csv file located at <APPIAN_HOME>/logs/data-metrics directory.

Cause

This issue has been addressed via AN-104637 in the following hotfixes/versions:

Action

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

Workaround

The following workaround can be used as a temporary measure until the hotfix or upgrade can be applied.

Edit the appian_log4j.properties file located at <APPIAN_HOME>/ear/suite.ear/resources, changing the following logger from:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=INFO

to:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=OFF

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: logging, known issues, administration, engines, fixed issues, Performance, infrastructure

DRAFT KB-XXXX Daily performance degradation and long 'getAppianObject' calls to the content engine caused by the data collection for the Expression Rule Test Cases data metrics log

Jordan Horwat — Wed, 22 Aug 2018 09:17:40 GMT

Revision 11 posted to Appian Knowledge Base by Jordan Horwat on 8/22/2018 9:17:40 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

Users experience short bursts of unresponsiveness and failed processes every day around the same time.
There are long getAppianObject calls to the content engine. These calls can be viewed in the db_CO1*.log file located at <APPIAN_HOME>/logs directory.
The times of the long getAppianObject calls in the db_CO1*.log file correspond with the timestamps in the expression_rule_test_cases.csv file located at <APPIAN_HOME>/logs/data-metrics directory.

Cause

This issue has been addressed via AN-104637 in the following hotfixes/versions:

Action

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

Workaround

The following workaround can be used as a temporary measure until the hotfix or upgrade can be applied.

Edit the appian_log4j.properties file located at <APPIAN_HOME>/ear/suite.ear/resources, changing the following logger from:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=INFO

to:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=OFF

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: logging, known issues, administration, engines, fixed issues, Performance, infrastructure

DRAFT KB-XXXX Daily performance degradation and long 'getAppianObject' calls to the content engine caused by the data collection for the Expression Rule Test Cases data metrics log

Tom Ryan — Wed, 22 Aug 2018 02:01:54 GMT

Revision 10 posted to Appian Knowledge Base by Tom Ryan on 8/22/2018 2:01: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

Users experience short bursts of unresponsiveness and failed processes every day around the same time.
There are long getAppianObject calls to the content engine. These calls can be viewed in the db_CO1*.log file located at <APPIAN_HOME>/logs directory.
The times of the long getAppianObject calls in the db_CO1*.log file correspond with the timestamps in the expression_rule_test_cases.csv file located at <APPIAN_HOME>/logs/data-metrics directory.

Cause

This issue has been addressed via AN-104637 in the following hotfixes/versions:

Appian 17.3 Hotfix Package H
Appian 17.4 Hotfix Package G
Appian 18.1 Hotfix Package C
Appian 18.2
Appian 18.3

Action

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

Workaround

The following workaround can be used as a temporary measure until the hotfix or upgrade can be applied.

Edit the appian_log4j.properties file located at <APPIAN_HOME>/ear/suite.ear/resources, changing the following logger from:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=INFO

to:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=OFF

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: logging, administration, engines, Performance, infrastructure

DRAFT KB-XXXX Daily performance degradation and long 'getAppianObject' calls to the content engine caused by the data collection for the Expression Rule Test Cases data metrics log

Jordan Horwat — Mon, 20 Aug 2018 18:06:16 GMT

Revision 1 posted to Appian Knowledge Base by Jordan Horwat on 8/20/2018 6:06:16 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

Users experience short bursts of unresponsiveness and failed processes every day around the same time.
There are long getAppianObject calls to the content engine. These calls can be viewed in the db_CO1*.log file located at <APPIAN_HOME>/logs/ directory.
The times of the long getAppianObject calls in the db_CO1*.log file correspond with the timestamps in the expression_rule_test_cases.csv file located at <APPIAN_HOME>/logs/data-metrics/ directory.

Cause

This issue has been addressed via AN-104637 in the following hotfixes/versions:

17.3 Hotfix Package H
17.4 Hotfix Package G
18.1 Hotfix Package C

Action

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

Workaround

Edit the appian_log4j.properties file located at <APPIAN_HOME>/ear/suite.ear/resources by changing the following logger from:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=INFO

to:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=OFF

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: logging, administration, engines, Performance, infrastructure

DRAFT KB-XXXX Daily performance degradation and long 'getAppianObject' calls to the content engine caused by the data collection for the Expression Rule Test Cases data metrics log

Jordan Horwat — Mon, 20 Aug 2018 14:20:53 GMT

Revision 9 posted to Appian Knowledge Base by Jordan Horwat on 8/20/2018 2:20:53 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

Users experience short bursts of unresponsiveness and failed processes every day around the same time.
There are long getAppianObject calls to the content engine. These calls can be viewed in the db_CO1*.log file located at <APPIAN_HOME>/logs directory.
The times of the long getAppianObject calls in the db_CO1*.log file correspond with the timestamps in the expression_rule_test_cases.csv file located at <APPIAN_HOME>/logs/data-metrics directory.

Cause

This issue has been addressed via AN-104637 in the following hotfixes/versions:

Appian 17.3 Hotfix Package H
Appian 17.4 Hotfix Package G
Appian 18.1 Hotfix Package C
Appian 18.2
Appian 18.3

Action

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

Workaround

Edit the appian_log4j.properties file located at <APPIAN_HOME>/ear/suite.ear/resources, changing the following logger from:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=INFO

to:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=OFF

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: logging, administration, engines, Performance, infrastructure

DRAFT KB-XXXX Daily performance degradation and long 'getAppianObject' calls to the content engine caused by the data collection for the Expression Rule Test Cases data metrics log

Jordan Horwat — Mon, 20 Aug 2018 14:20:41 GMT

Revision 8 posted to Appian Knowledge Base by Jordan Horwat on 8/20/2018 2:20:41 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

Users experience short bursts of unresponsiveness and failed processes every day around the same time.
There are long getAppianObject calls to the content engine. These calls can be viewed in the db_CO1*.log file located at <APPIAN_HOME>/logs directory.
The times of the long getAppianObject calls in the db_CO1*.log file correspond with the timestamps in the expression_rule_test_cases.csv file located at <APPIAN_HOME>/logs/data-metrics directory.

Cause

This issue has been addressed via AN-104637 in the following hotfixes/versions:

Appian 17.3 Hotfix Package H
Appian 17.4 Hotfix Package G
Appian 18.1 Hotfix Package C
Appian 18.2
Appian 18.3

Action

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

Workaround

Edit the appian_log4j.properties file located at <APPIAN_HOME>/ear/suite.ear/resources, changing the following logger from:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=INFO

to:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=OFF

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: logging, administration, engines, Performance, infrastructure

DRAFT KB-XXXX Daily performance degradation and long 'getAppianObject' calls to the content engine caused by the data collection for the Expression Rule Test Cases data metrics log

Jordan Horwat — Mon, 20 Aug 2018 14:14:54 GMT

Revision 7 posted to Appian Knowledge Base by Jordan Horwat on 8/20/2018 2:14:54 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

Users experience short bursts of unresponsiveness and failed processes every day around the same time.
There are long getAppianObject calls to the content engine. These calls can be viewed in the db_CO1*.log file located at <APPIAN_HOME>/logs directory.
The times of the long getAppianObject calls in the db_CO1*.log file correspond with the timestamps in the expression_rule_test_cases.csv file located at <APPIAN_HOME>/logs/data-metrics directory.

Cause

This issue has been addressed via AN-104637 in the following hotfixes/versions:

Appian 17.3 Hotfix Package H
Appian 17.4 Hotfix Package G
Appian 18.1 Hotfix Package C
Appian 18.2
Appian 18.3

Action

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

Workaround

Edit the appian_log4j.properties file located at <APPIAN_HOME>/ear/suite.ear/resources by changing the following logger from:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=INFO

to:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=OFF

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: logging, administration, engines, Performance, infrastructure

DRAFT KB-XXXX Daily performance degradation and long 'getAppianObject' calls to the content engine caused by the data collection for the Expression Rule Test Cases data metrics log

Jordan Horwat — Mon, 20 Aug 2018 14:14:05 GMT

Revision 6 posted to Appian Knowledge Base by Jordan Horwat on 8/20/2018 2:14:05 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

Users experience short bursts of unresponsiveness and failed processes every day around the same time.
There are long getAppianObject calls to the content engine. These calls can be viewed in the db_CO1*.log file located at <APPIAN_HOME>/logs directory.
The times of the long getAppianObject calls in the db_CO1*.log file correspond with the timestamps in the expression_rule_test_cases.csv file located at <APPIAN_HOME>/logs/data-metrics directory.

Cause

This issue has been addressed via AN-104637 in the following hotfixes/versions:

Appian 17.3 Hotfix Package H
Appian 17.4 Hotfix Package G
Appian 18.1 Hotfix Package C
Appian 18.2
Appian 18.3

Action

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

Workaround

Edit the appian_log4j.properties file located at <APPIAN_HOME>/ear/suite.ear/resources by changing the following logger:

Existing setting: log4j.logger.com.appian.data-metrics.expression-rule-test-cases=INFO
New setting: log4j.logger.com.appian.data-metrics.expression-rule-test-cases=OFF

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: logging, administration, engines, Performance, infrastructure

DRAFT KB-XXXX Daily performance degradation and long 'getAppianObject' calls to the content engine caused by the data collection for the Expression Rule Test Cases data metrics log

Jordan Horwat — Mon, 20 Aug 2018 14:12:28 GMT

Revision 5 posted to Appian Knowledge Base by Jordan Horwat on 8/20/2018 2:12:28 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

Users experience short bursts of unresponsiveness and failed processes every day around the same time.
There are long getAppianObject calls to the content engine. These calls can be viewed in the db_CO1*.log file located at <APPIAN_HOME>/logs directory.
The times of the long getAppianObject calls in the db_CO1*.log file correspond with the timestamps in the expression_rule_test_cases.csv file located at <APPIAN_HOME>/logs/data-metrics directory.

Cause

This issue has been addressed via AN-104637 in the following hotfixes/versions:

Appian 17.3 Hotfix Package H
Appian 17.4 Hotfix Package G
Appian 18.1 Hotfix Package C
Appian 18.2
Appian 18.3

Action

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

Workaround

Edit the appian_log4j.properties file located at <APPIAN_HOME>/ear/suite.ear/resources by changing the following logger from:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=INFO

to:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=OFF

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: logging, administration, engines, Performance, infrastructure

DRAFT KB-XXXX Daily performance degradation and long 'getAppianObject' calls to the content engine caused by the data collection for the Expression Rule Test Cases data metrics log

Jordan Horwat — Mon, 20 Aug 2018 14:08:39 GMT

Revision 4 posted to Appian Knowledge Base by Jordan Horwat on 8/20/2018 2:08:39 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

Users experience short bursts of unresponsiveness and failed processes every day around the same time.
There are long getAppianObject calls to the content engine. These calls can be viewed in the db_CO1*.log file located at <APPIAN_HOME>/logs directory.
The times of the long getAppianObject calls in the db_CO1*.log file correspond with the timestamps in the expression_rule_test_cases.csv file located at <APPIAN_HOME>/logs/data-metrics directory.

Cause

This issue has been addressed via AN-104637 in the following hotfixes/versions:

17.3 Hotfix Package H
17.4 Hotfix Package G
18.1 Hotfix Package C

Action

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

Workaround

Edit the appian_log4j.properties file located at <APPIAN_HOME>/ear/suite.ear/resources by changing the following logger from:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=INFO

to:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=OFF

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: logging, administration, engines, Performance, infrastructure

DRAFT KB-XXXX Daily performance degradation and long 'getAppianObject' calls to the content engine caused by the data collection for the Expression Rule Test Cases data metrics log

Jordan Horwat — Mon, 20 Aug 2018 14:07:57 GMT

Revision 3 posted to Appian Knowledge Base by Jordan Horwat on 8/20/2018 2:07:57 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

Users experience short bursts of unresponsiveness and failed processes every day around the same time.
There are long getAppianObject calls to the content engine. These calls can be viewed in the db_CO1*.log file located at <APPIAN_HOME>/logs directory.
The times of the long getAppianObject calls in the db_CO1*.log file correspond with the timestamps in the expression_rule_test_cases.csv file located at <APPIAN_HOME>/logs/data-metrics directory.

Cause

This issue has been addressed via AN-104637 in the following hotfixes/versions:

17.3 Hotfix Package H
17.4 Hotfix Package G
18.1 Hotfix Package C

Action

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

Workaround

Edit the appian_log4j.properties file located at <APPIAN_HOME>/ear/suite.ear/resources by changing the following logger from:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=INFO

to:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=OFF

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: logging, administration, engines, Performance, infrastructure

DRAFT KB-XXXX Daily performance degradation and long 'getAppianObject' calls to the content engine caused by the data collection for the Expression Rule Test Cases data metrics log

Jordan Horwat — Mon, 20 Aug 2018 14:06:40 GMT

Revision 2 posted to Appian Knowledge Base by Jordan Horwat on 8/20/2018 2:06:40 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

Users experience short bursts of unresponsiveness and failed processes every day around the same time.
There are long getAppianObject calls to the content engine. These calls can be viewed in the db_CO1*.log file located at <APPIAN_HOME>/logs/ directory.
The times of the long getAppianObject calls in the db_CO1*.log file correspond with the timestamps in the expression_rule_test_cases.csv file located at <APPIAN_HOME>/logs/data-metrics/ directory.

Cause

This issue has been addressed via AN-104637 in the following hotfixes/versions:

17.3 Hotfix Package H
17.4 Hotfix Package G
18.1 Hotfix Package C

Action

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

Workaround

Edit the appian_log4j.properties file located at <APPIAN_HOME>/ear/suite.ear/resources by changing the following logger from:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=INFO

to:

log4j.logger.com.appian.data-metrics.expression-rule-test-cases=OFF

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: logging, administration, engines, Performance, infrastructure