Appian engines fail to reach RUNNING state, PRIMARY mode, and the following exception is printed in the service_manager.log file (located at <APPIAN_HOME>/logs):
java.lang.IllegalArgumentException: byte array given isn't the right length. Expected 256, was 257. at com.google.common.base.Preconditions.checkArgument(Preconditions.java:146) ~[guava-19.0.jar:?] at com.appian.komodo.gateway.model.SecurityToken.fromInputStream(SecurityToken.java:49) ~[core-1.83.0.jar:1.83.0] at com.appian.komodo.config.ConfigurationModule.provideSecurityToken(ConfigurationModule.java:212) ~[core-1.83.0.jar:1.83.0] at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:31) ~[core-1.83.0.jar:1.83.0] at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:10) ~[core-1.83.0.jar:1.83.0]
The alpha-numeric string in the Appian engine security token, appian.sec (located at <APPIAN_HOME>/ear/suite.ear/conf), is being read as having 257 characters instead of 256 characters. This can happen when the appian.sec file is opened, even when the string contained in the file is not altered.
Complete one of the following steps to resolve this issue:
Note: for High Availability and Distributed Installations, the appian.sec file must be exactly the same across each server to enable authorized connections between the engines and specified application servers.
This article applies to Appian 17.3 and later.
Last Reviewed: May 2018
© 2023 Appian. All rights reserved.