When trying to initiate some processes in an environment, a 500 - Internal Server Error is displayed and the following errors are seen in the application server log:
500 - Internal Server Error
ERROR com.appiancorp.process.engine.StartProcessByEventRequest - Could not start process model [draftId=<ID>, version=<version>, userContext=<user>]com.appian.komodo.api.exceptions.SignalException: domain
ERROR com.appiancorp.common.config.ConfigObject - An error occurred while trying to initialize the config LoadExceptionHandling [0ms] [resources 16ms] com.appian.komodo.api.exceptions.SignalException: domain at
When checking CPU usage on the server hosting the Appian engines, a single execution engine is found to be running at 100% CPU. Steps to verify this are listed below:
This issue occurs when one of the below engine performance logs reaches 10 megabytes in size:
These logs can be found in the <APPIAN_HOME>/logs/perflogs directory. These logs will roll over anytime an execution engine is restarted. Therefore, it has been calculated that this behavior should only occur if an execution engine has been running continuously for no less than approximately 60 days.
The reason these logs can cause an execution engine to max out at 100% CPU utilization is a result of how select values in these logs are calculated. Transient tables within the execution engine that populate values in these logs become too massive to scale any further, which causes the engine to lock while trying to process the data. This issue has been addressed via AN-146311 in the following hotfixes/versions:
Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.
Open a case with Appian Support and note to the case description that you are experiencing behavior in line with this article.
This issue can be resolved by restarting the environment. To avoid downtime in the environment, moving the above mentioned log files to a directory other than <APPIAN_HOME>/logs/perflogs and restarting the afflicted engine will resolve this issue. A single execution engine can be restarted with the following procedures:
./stop.sh (.bat) -p <PASSWORD> -s executionXX
./start.sh (.bat) -p <PASSWORD> -s executionXX
If the above steps fail or take an extended amount of time, follow the procedures below to forcibly kill and restart the engine:
kill -9 <PID>
This article applies to Appian 18.3 to 19.4
Last Reviewed: June 2020
© 2022 Appian. All rights reserved.