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
| 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
getAppianObjectcalls to the content engine. These calls can be viewed in the db_CO1*.log file located at<APPIAN_HOME>/logsdirectory. - The times of the long
getAppianObjectcalls in the db_CO1*.log file correspond with the timestamps in the expression_rule_test_cases.csv file located at<APPIAN_HOME>/logs/data-metricsdirectory.
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 from Appian 17.2 to Appian 18.1.
Last Reviewed: August 2018
