KB-1560 "loadMetric.threshold has type STRING rather than NUMBER" causes Service Manager startup to fail

Jordan Horwat — Tue, 29 Jan 2019 14:49:31 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 1/29/2019 2:49:31 PM

Symptoms

When starting the Appian services, the startup stalls at "Waiting for Service Manager to launch," and the following exception appears in the <APPIAN_HOME>/logs/service_manager.log file:

ERROR com.appian.komodo.Bootstrap - Uncaught error in thread. com.typesafe.config.ConfigException$WrongType:<APPIAN_HOME>/conf/custom.properties: transaction has type STRING rather than NUMBER

A specific "Caused by:" statement for this error is shown below:

Caused by: com.typesafe.config.ConfigException$WrongType: <APPIAN_HOME>/ear/suite.ear/conf/custom.properties: loadMetric.threshold has type STRING rather than NUMBER

Cause

Service Manager has encountered an unexpected property value in the custom.properties file located at <APPIAN_HOME>/conf/. Specifically, a property listed in custom.properties is set equal to a value that is being read as a string rather than a number.

In the example above, the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC property listed in custom.properties is set equal to a value that is being read as a string rather than a number. More information about this setting can be found in the Configuring the Process Engine Servers documentation.

Action

Review the custom.properties file to ensure all properties have expected values and that there are no unexpected trailing characters appending the properties.

For the example above, ensure that the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC property listed in custom.properties is set equal to an integer value.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: January 2019

Tags: installation, infrastructure, service manager

KB-1560 "loadMetric.threshold has type STRING rather than NUMBER" causes Service Manager startup to fail

Jordan Horwat — Tue, 29 Jan 2019 14:48:04 GMT

Revision 10 posted to Appian Knowledge Base by Jordan Horwat on 1/29/2019 2:48:04 PM

Symptoms

When starting the Appian services, the startup stalls at "Waiting for Service Manager to launch," and the following exception appears in the <APPIAN_HOME>/logs/service_manager.log file:

ERROR com.appian.komodo.Bootstrap - Uncaught error in thread. com.typesafe.config.ConfigException$WrongType:<APPIAN_HOME>/conf/custom.properties: transaction has type STRING rather than NUMBER

A specific "Caused by:" statement for this error is shown below:

Caused by: com.typesafe.config.ConfigException$WrongType: <APPIAN_HOME>/ear/suite.ear/conf/custom.properties: loadMetric.threshold has type STRING rather than NUMBER

Cause

Action

Review the custom.properties file to ensure all properties have expected values and that there are no unexpected trailing characters appending the properties.

For the example above, ensure that the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC property listed in custom.properties is set equal to an integer value.

Affected Version

This article applies to Appian 17.3 and later.

Last Reviewed: January 2019

Tags: installation, infrastructure, service manager

KB-1560 "loadMetric.threshold has type STRING rather than NUMBER" causes Service Manager startup to fail

Jordan Horwat — Tue, 29 Jan 2019 14:47:52 GMT

Revision 9 posted to Appian Knowledge Base by Jordan Horwat on 1/29/2019 2:47:52 PM

Symptoms

When starting the Appian services, the startup stalls at "Waiting for Service Manager to launch," and the following exception appears in the <APPIAN_HOME>/logs/service_manager.log file:

ERROR com.appian.komodo.Bootstrap - Uncaught error in thread. com.typesafe.config.ConfigException$WrongType:<APPIAN_HOME>/conf/custom.properties: transaction has type STRING rather than NUMBER

A specific "Caused by:" statement for this error is shown below:

Caused by: com.typesafe.config.ConfigException$WrongType: <APPIAN_HOME>/ear/suite.ear/conf/custom.properties: loadMetric.threshold has type STRING rather than NUMBER

Cause

Action

Review the custom.properties file to ensure all properties have expected values and that there are no unexpected trailing characters appending the properties.

For the example above, ensure that the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC property listed in custom.properties is set equal to an integer value.

Affected Version

This article applies to Appian 17.3 and later.

Last Reviewed: January 2019

Tags: installation, infrastructure, service manager

KB-1560 "loadMetric.threshold has type STRING rather than NUMBER" causes Service Manager startup to fail

Jordan Horwat — Tue, 27 Nov 2018 11:58:56 GMT

Revision 8 posted to Appian Knowledge Base by Jordan Horwat on 11/27/2018 11:58:56 AM

Symptoms

When starting the Appian services, the startup stalls at "Waiting for Service Manager to launch," and the following exception appears in the <APPIAN_HOME>/logs/service_manager.log file:

java.lang.IllegalStateException: Expected the service to be TERMINATED, but the service has FAILED
.
.
.
Caused by: com.typesafe.config.ConfigException$WrongType: <APPIAN_HOME>/ear/suite.ear/conf/custom.properties: loadMetric.threshold has type STRING rather than NUMBER

Cause

The server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC property listed in custom.properties is set equal to a value that is being read as a string rather than a number. More information about this setting can be found in the Configuring the Process Engine Servers documentation.

Action

Ensure that the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC property listed in custom.properties is set equal to an integer value.

Affected Version

This article applies to Appian 17.3 and later.

Last Reviewed: April 2018

Tags: installation, infrastructure, service manager

KB-1560 "loadMetric.threshold has type STRING rather than NUMBER" causes Service Manager startup to fail

Jordan Horwat — Tue, 27 Nov 2018 11:58:19 GMT

Revision 7 posted to Appian Knowledge Base by Jordan Horwat on 11/27/2018 11:58:19 AM

Symptoms

When starting the Appian services, the startup stalls at "Waiting for Service Manager to launch," and the following exception appears in the <APPIAN_HOME>/logs/service_manager.log:

java.lang.IllegalStateException: Expected the service to be TERMINATED, but the service has FAILED
.
.
.
Caused by: com.typesafe.config.ConfigException$WrongType: <APPIAN_HOME>/ear/suite.ear/conf/custom.properties: loadMetric.threshold has type STRING rather than NUMBER

Cause

Action

Ensure that the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC property listed in custom.properties is set equal to an integer value.

Affected Version

This article applies to Appian 17.3 and later.

Last Reviewed: April 2018

Tags: installation, infrastructure, service manager

KB-1560 "loadMetric.threshold has type STRING rather than NUMBER" causes Service Manager startup to fail

Jordan Horwat — Mon, 23 Jul 2018 12:43:39 GMT

Revision 6 posted to Appian Knowledge Base by Jordan Horwat on 7/23/2018 12:43:39 PM

Symptoms

When starting the Appian services, the startup stalls at "Waiting for Service Manager to launch," and the following exception appears in the application server log:

java.lang.IllegalStateException: Expected the service to be TERMINATED, but the service has FAILED
.
.
.
Caused by: com.typesafe.config.ConfigException$WrongType: <APPIAN_HOME>/ear/suite.ear/conf/custom.properties: loadMetric.threshold has type STRING rather than NUMBER

Cause

Action

Ensure that the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC property listed in custom.properties is set equal to an integer value.

Affected Version

This article applies to Appian 17.3 and later.

Last Reviewed: April 2018

Tags: installation, infrastructure, service manager

KB-1560 "loadMetric.threshold has type STRING rather than NUMBER" causes Service Manager startup to fail

Nick Vigilante — Thu, 26 Apr 2018 13:26:07 GMT

Revision 5 posted to Appian Knowledge Base by Nick Vigilante on 4/26/2018 1:26:07 PM

Symptoms

When starting the Appian services, the startup stalls at "Waiting for Service Manager to launch," and the following exception appears in the application server log:

java.lang.IllegalStateException: Expected the service to be TERMINATED, but the service has FAILED
.
.
.
Caused by: com.typesafe.config.ConfigException$WrongType: <APPIAN_HOME>/ear/suite.ear/conf/custom.properties: loadMetric.threshold has type STRING rather than NUMBER

Cause

Action

Ensure that the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC property listed in custom.properties is set equal to an integer value.

Affected Version

This article applies to Appian 17.3 and later.

Last Reviewed: April 2018

Tags: service manager

DRAFT KB-XXX "loadMetric.threshold has type STRING rather than NUMBER" causes Service Manager startup to fail

Jordan Horwat — Thu, 26 Apr 2018 09:13:33 GMT

Revision 4 posted to Appian Knowledge Base by Jordan Horwat on 4/26/2018 9:13:33 AM

Symptoms

When starting the Appian services, the startup stalls at "Waiting for Service Manager to launch," and the following exception appears in the application server log:

java.lang.IllegalStateException: Expected the service to be TERMINATED, but the service has FAILED
.
.
.
Caused by: com.typesafe.config.ConfigException$WrongType: <APPIAN_HOME>/ear/suite.ear/conf/custom.properties: loadMetric.threshold has type STRING rather than NUMBER

Cause

Action

Ensure that the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC property listed in custom.properties is set equal to an integer value.

Affected Version

This article applies to Appian 17.3 and later.

Last Reviewed: April 2018

Tags: service manager

DRAFT KB-XXX "loadMetric.threshold has type STRING rather than NUMBER" causes Service Manager startup to fail

Jordan Horwat — Wed, 25 Apr 2018 17:46:45 GMT

Revision 3 posted to Appian Knowledge Base by Jordan Horwat on 4/25/2018 5:46:45 PM

Symptoms

When starting the Appian services, the startup stalls at "Waiting for Service Manager to launch," and the following exception appears in the application server log:

java.lang.IllegalStateException: Expected the service to be TERMINATED, but the service has FAILED
.
.
.
Caused by: com.typesafe.config.ConfigException$WrongType: <APPIAN_HOME>/ear/suite.ear/conf/custom.properties: loadMetric.threshold has type STRING rather than NUMBER

Cause

The server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC= line listed in custom.properties is set equal to a value that is being read as a string rather than a number. More information about this setting can be found in the Configuring the Process Engine Servers documentation.

Action

Ensure that the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC= line listed in custom.properties is set equal to an integer value.

Affected Version

This article applies to Appian 17.3 and later.

Last Reviewed: April 2018

Tags: service manager

DRAFT KB-XXX "loadMetric.threshold has type STRING rather than NUMBER" causes Service Manager startup to fail

Jordan Horwat — Wed, 25 Apr 2018 17:46:24 GMT

Revision 2 posted to Appian Knowledge Base by Jordan Horwat on 4/25/2018 5:46:24 PM

Symptoms

When starting the Appian services, the startup stalls at "Waiting for Service Manager to launch," and the following exception appears in the application server log:

java.lang.IllegalStateException: Expected the service to be TERMINATED, but the service has FAILED
.
.
.
Caused by: com.typesafe.config.ConfigException$WrongType: <APPIAN_HOME>/ear/suite.ear/conf/custom.properties: loadMetric.threshold has type STRING rather than NUMBER

Cause

Action

Ensure that the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC= line listed in custom.properties is set equal to an integer value.

Affected Version

This article applies to Appian 17.3 and later.

Last Reviewed: April 2018

Tags: service manager

DRAFT KB-XXX "loadMetric.threshold has type STRING rather than NUMBER" causes Service Manager startup to fail

Jordan Horwat — Tue, 24 Apr 2018 18:55:49 GMT

Revision 1 posted to Appian Knowledge Base by Jordan Horwat on 4/24/2018 6:55:49 PM

Symptoms

When starting the Appian services, the startup stalls at "Waiting for Service Manager to launch," and the following exception appears in the application server log:

java.lang.IllegalStateException: Expected the service to be TERMINATED, but the service has FAILED
.
.
.
Caused by: com.typesafe.config.ConfigException$WrongType: <APPIAN_HOME>/ear/suite.ear/conf/custom.properties: loadMetric.threshold has type STRING rather than NUMBER

Cause

The server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC= line listed in custom.properties is set equal to a value that is being read as a string rather than a number. If this line is set equal to a variable that is defined (as an integer) in a separate configuration file, this file containing the integer value is not being properly implemented/read.

Action

Ensure that the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC= line listed in custom.properties is set equal to an integer value, whether the integer is listed explicitly in custom.properties or through a variable that calls an integer value from a separate configuration file.

Workaround

If a variable (that is defined in a separate configuration file) is being used to define this value, and the separate configuration file is not being properly implemented/read, set server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC= equal to an integer value explicitly in custom.properties.

Affected Version

This article applies to Appian 17.3 and later.

Last Reviewed: April 2018

Tags: service manager