KB-2304 Engines fail to start with java.nio.charset.MalformedInputException error

pauline.delacruz — Wed, 24 Apr 2024 16:23:13 GMT

Current Revision posted to Appian Knowledge Base by pauline.delacruz on 4/24/2024 4:23:13 PM

Symptoms

When starting Service Manager and engines, the following error is thrown in the service_manager.log and the engines fail to start:

YYYY-MM-DD HH:MM:SS,mmm [engine-supervisor-<ENGINE>-0] ERROR com.appian.komodo.engine.EngineSupervisor - Engine component creation for <ENGINE> has failed.
java.nio.charset.MalformedInputException: Input length = 1

Cause

This is caused by the custom.properties file, located in <APPIAN_HOME>/conf/custom.properties, not being encoded in UTF-8 format. This could happen if the file was modified and saved using an editor that does not use UTF-8 as its default encoding.

Action

Recreate custom.properties as a UTF-8 encoded file using a text editor.
1. For example, if using Notepad on Windows, choose UTF-8 under the Encoding option when saving the file.
Replace the current file with the UTF-8 encoded one and restart the engines.

Affected Versions

This article applies to all versions of Appian on Linux.

Last Reviewed: April 2024

Tags: engines, utf-8, infrastructure, service manager

SP-9783 KB-XXXX Engines fail to start with java.nio.charset.MalformedInputException error

pauline.delacruz — Tue, 23 Apr 2024 16:45:38 GMT

Revision 8 posted to Appian Knowledge Base by pauline.delacruz on 4/23/2024 4:45:38 PM

Symptoms

When starting Service Manager and engines, the following error is thrown in the service_manager.log and the engines fail to start:

YYYY-MM-DD HH:MM:SS,mmm [engine-supervisor-<ENGINE>-0] ERROR com.appian.komodo.engine.EngineSupervisor - Engine component creation for <ENGINE> has failed.
java.nio.charset.MalformedInputException: Input length = 1

Cause

Action

Recreate custom.properties as a UTF-8 encoded file using a text editor.
1. For example, if using Notepad on Windows, choose UTF-8 under the Encoding option when saving the file.
Replace the current file with the UTF-8 encoded one and restart the engines.

Affected Versions

This article applies to all versions of Appian on Linux.

Last Reviewed: April 2024

Tags: engines, utf-8, infrastructure, service manager

SP-9783 Engines fail to start with java.nio.charset.MalformedInputException error

pauline.delacruz — Tue, 23 Apr 2024 16:44:14 GMT

Revision 7 posted to Appian Knowledge Base by pauline.delacruz on 4/23/2024 4:44:14 PM

Symptoms

When starting Service Manager and engines, the following error is thrown in the service_manager.log and the engines fail to start:

YYYY-MM-DD HH:MM:SS,mmm [engine-supervisor-<ENGINE>-0] ERROR com.appian.komodo.engine.EngineSupervisor - Engine component creation for <ENGINE> has failed.
java.nio.charset.MalformedInputException: Input length = 1

Cause

Action

Recreate custom.properties as a UTF-8 encoded file using a text editor.
1. For example, if using Notepad on Windows, choose UTF-8 under the Encoding option when saving the file.
Replace the current file with the UTF-8 encoded one and restart the engines.

Affected Versions

This article applies to all versions of Appian on Linux.

Last Reviewed: April 2024

Tags: engines, utf-8, infrastructure, service manager

SP-9783 Engines fail to start with java.nio.charset.MalformedInputException error

Yiyi Tao — Mon, 22 Apr 2024 19:45:23 GMT

Revision 6 posted to Appian Knowledge Base by Yiyi Tao on 4/22/2024 7:45:23 PM

Symptoms

When starting Service Manager and engines, the following error is thrown in the service_manager.log and the engines fail to start:

YYYY-MM-DD HH:MM:SS,mmm [engine-supervisor-<ENGINE>-0] ERROR com.appian.komodo.engine.EngineSupervisor - Engine component creation for <ENGINE> has failed.
java.nio.charset.MalformedInputException: Input length = 1

Cause

This is caused by the custom.properties file, located in <APPIAN_HOME>/conf/custom.properties, not being encoded in UTF-8 format. This could happen if someone edited and saved the file using an editor that doesn't use UTF-8 as its default encoding.

Action

Recreate custom.properties as a UTF-8 encoded file using a text editor. For instance, if using Notepad on Windows, choose UTF-8 under the Encoding option when saving the file.
Replace the current file with the UTF-8 encoded one and restart the engines.

Affected Versions

This article applies to all versions of Appian on Linux.

Last Reviewed: April 2024

Tags: engines, utf-8, infrastructure, service manager

SP-9783 Engines fail to start with java.nio.charset.MalformedInputException error

pauline.delacruz — Wed, 03 Apr 2024 13:26:33 GMT

Revision 5 posted to Appian Knowledge Base by pauline.delacruz on 4/3/2024 1:26:33 PM

Symptoms

When starting Service Manager and engines, the following error is thrown in the service_manager.log and the engines fail to start:

YYYY-MM-DD HH:MM:SS,mmm [engine-supervisor-<ENGINE>-0] ERROR com.appian.komodo.engine.EngineSupervisor - Engine component creation for <ENGINE> has failed.
java.nio.charset.MalformedInputException: Input length = 1

Cause

This is caused by the custom.properties file, located in <APPIAN_HOME>/conf/custom.properties, being encoded using a format that is not UTF-8.

Action

Recreate custom.properties as UTF-8 encoded file.
Replace the current file with the UTF-8 encoded one and restart the engines.

Affected Versions

This article applies to all versions of Appian on Linux.

Last Reviewed: April 2024

Tags: engines, utf-8, infrastructure, service manager

SP-9783 Engines fail to start with java.nio.charset.MalformedInputException error

pauline.delacruz — Wed, 03 Apr 2024 13:25:32 GMT

Revision 4 posted to Appian Knowledge Base by pauline.delacruz on 4/3/2024 1:25:32 PM

Symptoms

When starting Service Manager and engines, the following error is thrown in the service_manager.log and the engines fail to start:

YYYY-MM-DD HH:MM:SS,mmm [engine-supervisor-<ENGINE>-0] ERROR com.appian.komodo.engine.EngineSupervisor - Engine component creation for <ENGINE> has failed.
java.nio.charset.MalformedInputException: Input length = 1

Cause

This is caused by the custom.properties file, found in <APPIAN_HOME>/conf/custom.properties, being encoded using a format that is not UTF-8.

Action

Recreate custom.properties as UTF-8 encoded file.
Replace the current file with the UTF-8 encoded one and restart the engines.

Affected Versions

This article applies to all versions of Appian on Linux.

Last Reviewed: April 2024

Tags: engines, utf-8, infrastructure, service manager

SP-9783 Engines fail to start with java.nio.charset.MalformedInputException error

pauline.delacruz — Wed, 03 Apr 2024 13:13:44 GMT

Revision 3 posted to Appian Knowledge Base by pauline.delacruz on 4/3/2024 1:13:44 PM

Symptoms

When starting Service Manager and engines, the following error is thrown in the service_manager.log and the engines fail to start:

YYYY-MM-DD HH:MM:SS,mmm [engine-supervisor-<ENGINE>-0] ERROR com.appian.komodo.engine.EngineSupervisor - Engine component creation for <ENGINE> has failed.
java.nio.charset.MalformedInputException: Input length = 1

Cause

This is caused by the custom.properties file (Self-managed: <APPIAN_HOME>/conf/custom.properties, Cloud: /usr/local/appian/ae/conf/custom.properties) being encoded using a format that is not UTF-8.

Action

Recreate custom.properties as UTF-8 encoded file.
Replace the current file with the UTF-8 encoded one and restart the engines.

Affected Versions

This article applies to all versions of Appian on Linux.

Last Reviewed: April 2024

Tags: engines, utf-8, infrastructure, service manager

SP-9783 Engines fail to start with java.nio.charset.MalformedInputException error

Yiyi Tao — Tue, 02 Apr 2024 21:32:00 GMT

Revision 2 posted to Appian Knowledge Base by Yiyi Tao on 4/2/2024 9:32:00 PM

Symptoms

When starting Service Manager and engines, the following error is thrown in the service_manager.log and the engines fail to start:

YYYY-MM-DD HH:MM:SS,FFF [engine-supervisor-<ENGINE>-0] ERROR com.appian.komodo.engine.EngineSupervisor - Engine component creation for <ENGINE> has failed.
java.nio.charset.MalformedInputException: Input length = 1

Cause

This is caused by the custom.properties (Self-managed: <APPIAN_HOME>/conf/custom.properties, Cloud: /usr/local/appian/ae/conf/custom.properties) being encoded using a format that is not UTF-8.

Action

Recreate custom.properties as utf-8 encoded file. Replace the current file with the utf-8 encoded one and restart the engines.

Affected Versions

This article applies to all versions of Appian on Linux.

Last Reviewed: April 2024

SP-9783 Engines fail to start with java.nio.charset.MalformedInputException error

Yiyi Tao — Tue, 02 Apr 2024 21:31:21 GMT

Revision 1 posted to Appian Knowledge Base by Yiyi Tao on 4/2/2024 9:31:21 PM

Symptoms

When starting Service Manager and engines, the following error is thrown in the service_manager.log and the engines fail to start:

YYYY-MM-DD HH:MM:SS,FFF [engine-supervisor-<ENGINE>-0] ERROR com.appian.komodo.engine.EngineSupervisor - Engine component creation for <ENGINE> has failed.
java.nio.charset.MalformedInputException: Input length = 1

Cause

Action

Recreate custom.properties as utf-8 encoded file. Replace the current file with the utf-8 encoded one and restart the Appian components.

Affected Versions

This article applies to all versions of Appian on Linux.

Last Reviewed: April 2024