KB-1823 Unable to start the application server after an upgrade due to Invalid Security Token

Jordan Horwat — Fri, 28 Dec 2018 13:44:30 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 12/28/2018 1:44:30 PM

Symptoms

During an Appian upgrade, the application server is unable to start and the following error appears on the application server log:

ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Unexpected exception while handling message for personalization (localhost:5012)
com.appiancorp.kougar.driver.exceptions.TcpException: java.io.EOFException: Socket returned no more data at end of stream

...

com.appiancorp.kougar.driver.exceptions.SafeRetryException: Unable to acquire a Read connection. Safe to retry.
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:154)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:89)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1147)
... 71 more

In the service_manager.log file located at <APPIAN_HOME>/logs/, the following warning is present:

com.appian.komodo.gateway.handler.codec.SecurityTokenDecoder - Invalid Security Token.

Cause

This error appears when the security token has been modified or deleted during the upgrade. In particular, it happens when the security token has been changed after starting Service Manager, causing the engines to refuse the connection with the application server. The following documentation provides additional details about the security token.

Action

If this occurs during the upgrade, stop all the components and copy the security token from the backup folder to the correct directory in the new installation folder. The security token should be in the <APPIAN_HOME>/conf/ directory for Appian 18.2 and later or in the <APPIAN_HOME>/ear/suite.ear/conf/ directory for Appian version 18.1 and earlier.

If a backup does not exist, it is also possible to generate a new security token, as mentioned in the documentation.

Note: For distributed environments, the security token must match across all servers in the environment. This is further explained in this documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: application server, upgrade, infrastructure, service manager

KB-1823 Unable to start the application server after an upgrade due to Invalid Security Token

Jordan Horwat — Fri, 28 Dec 2018 18:42:08 GMT

Revision 9 posted to Appian Knowledge Base by Jordan Horwat on 12/28/2018 6:42:08 PM

Symptoms

During an Appian upgrade, the application server is unable to start and the following error appears on the application server log:

ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Unexpected exception while handling message for personalization (localhost:5012)
com.appiancorp.kougar.driver.exceptions.TcpException: java.io.EOFException: Socket returned no more data at end of stream

...

com.appiancorp.kougar.driver.exceptions.SafeRetryException: Unable to acquire a Read connection. Safe to retry.
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:154)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:89)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1147)
... 71 more

In the <APPIAN_HOME>/logs/service_manager.log file, the following warning is present:

com.appian.komodo.gateway.handler.codec.SecurityTokenDecoder - Invalid Security Token.

Cause

Action

If a backup does not exist, it is also possible to generate a new security token, as mentioned in the documentation.

Note: For distributed environments, the security token must match across all servers in the environment. This is further explained in this documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: application server, upgrade, infrastructure, service manager

KB-1823 Unable to start the application server after an upgrade due to Invalid Security Token

Jordan Horwat — Fri, 28 Dec 2018 13:44:11 GMT

Revision 10 posted to Appian Knowledge Base by Jordan Horwat on 12/28/2018 1:44:11 PM

Symptoms

During an Appian upgrade, the application server is unable to start and the following error appears on the application server log:

ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Unexpected exception while handling message for personalization (localhost:5012)
com.appiancorp.kougar.driver.exceptions.TcpException: java.io.EOFException: Socket returned no more data at end of stream

...

com.appiancorp.kougar.driver.exceptions.SafeRetryException: Unable to acquire a Read connection. Safe to retry.
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:154)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:89)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1147)
... 71 more

In the service_manager.log file located at <APPIAN_HOME>/logs/, the following warning is present:

com.appian.komodo.gateway.handler.codec.SecurityTokenDecoder - Invalid Security Token.

Cause

Action

If a backup does not exist, it is also possible to generate a new security token, as mentioned in the documentation.

Note: For distributed environments, the security token must match across all servers in the environment. This is further explained in this documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: application server, upgrade, infrastructure, service manager

KB-1823 Unable to start the application server after an upgrade due to invalid security token

Jordan Horwat — Fri, 28 Dec 2018 13:41:28 GMT

Revision 8 posted to Appian Knowledge Base by Jordan Horwat on 12/28/2018 1:41:28 PM

Symptoms

During an Appian upgrade, the application server is unable to start and the following error appears on the application server log:

ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Unexpected exception while handling message for personalization (localhost:5012)
com.appiancorp.kougar.driver.exceptions.TcpException: java.io.EOFException: Socket returned no more data at end of stream

...

com.appiancorp.kougar.driver.exceptions.SafeRetryException: Unable to acquire a Read connection. Safe to retry.
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:154)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:89)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1147)
... 71 more

In the <APPIAN_HOME>/logs/service_manager.log file, the following warning is present:

com.appian.komodo.gateway.handler.codec.SecurityTokenDecoder - Invalid Security Token.

Cause

Action

If a backup does not exist, it is also possible to generate a new security token, as mentioned in the documentation.

Note: For distributed environments, the security token must match across all servers in the environment. This is further explained in this documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: application server, upgrade, infrastructure, service manager

DRAFT KB-XXXX Unable to start the application server after an upgrade due to invalid security token

Jordan Horwat — Fri, 28 Dec 2018 13:39:25 GMT

Revision 7 posted to Appian Knowledge Base by Jordan Horwat on 12/28/2018 1:39:25 PM

Symptoms

During an Appian upgrade, the application server is unable to start and the following error appears on the application server log:

ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Unexpected exception while handling message for personalization (localhost:5012)
com.appiancorp.kougar.driver.exceptions.TcpException: java.io.EOFException: Socket returned no more data at end of stream

...

com.appiancorp.kougar.driver.exceptions.SafeRetryException: Unable to acquire a Read connection. Safe to retry.
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:154)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:89)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1147)
... 71 more

In the <APPIAN_HOME>/logs/service_manager.log file, the following warning is present:

com.appian.komodo.gateway.handler.codec.SecurityTokenDecoder - Invalid Security Token.

Cause

Action

If a backup does not exist, it is also possible to generate a new security token, as mentioned in the documentation.

Note: For distributed environments, the security token must match across all servers in the environment. This is further explained in this documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: application server, upgrade, infrastructure, service manager

DRAFT KB-XXXX Unable to start the application server after an upgrade due to invalid security token

Jordan Horwat — Mon, 17 Dec 2018 16:05:01 GMT

Revision 6 posted to Appian Knowledge Base by Jordan Horwat on 12/17/2018 4:05:01 PM

Symptoms

During an Appian upgrade, the application server is unable to start and the following error appears on the application server log:

ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Unexpected exception while handling message for personalization (localhost:5012)
com.appiancorp.kougar.driver.exceptions.TcpException: java.io.EOFException: Socket returned no more data at end of stream

...

com.appiancorp.kougar.driver.exceptions.SafeRetryException: Unable to acquire a Read connection. Safe to retry.
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:154)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:89)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1147)
... 71 more

In the <APPIAN_HOME>/logs/service_manager.log file, the following warning is present:

com.appian.komodo.gateway.handler.codec.SecurityTokenDecoder - Invalid Security Token.

Cause

Action

If a backup does not exist, it is also possible to generate a new security token, as mentioned in the documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: application server, upgrade, infrastructure, service manager

DRAFT KB-XXXX Unable to start the application server after an upgrade due to invalid security token

Jordan Horwat — Mon, 17 Dec 2018 16:04:30 GMT

Revision 5 posted to Appian Knowledge Base by Jordan Horwat on 12/17/2018 4:04:30 PM

Symptoms

The application server is unable to start and the following error appears on the application server log:

ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Unexpected exception while handling message for personalization (localhost:5012)
com.appiancorp.kougar.driver.exceptions.TcpException: java.io.EOFException: Socket returned no more data at end of stream

...

com.appiancorp.kougar.driver.exceptions.SafeRetryException: Unable to acquire a Read connection. Safe to retry.
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:154)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:89)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1147)
... 71 more

In the <APPIAN_HOME>/logs/service_manager.log file, the following warning is present:

com.appian.komodo.gateway.handler.codec.SecurityTokenDecoder - Invalid Security Token.

Cause

Action

If a backup does not exist, it is also possible to generate a new security token, as mentioned in the documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: application server, upgrade, infrastructure, service manager

DRAFT KB-XXXX Unable to start the application server after an upgrade due to invalid security token

Jordan Horwat — Mon, 17 Dec 2018 16:04:00 GMT

Revision 4 posted to Appian Knowledge Base by Jordan Horwat on 12/17/2018 4:04:00 PM

Symptoms

The application server is unable to start and the following error appears on the application server log:

ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Unexpected exception while handling message for personalization (localhost:5012)
com.appiancorp.kougar.driver.exceptions.TcpException: java.io.EOFException: Socket returned no more data at end of stream

...

com.appiancorp.kougar.driver.exceptions.SafeRetryException: Unable to acquire a Read connection. Safe to retry.
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:154)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:89)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1147)
... 71 more

In the <APPIAN_HOME>/logs/service_manager.log file, the following warning is present:

com.appian.komodo.gateway.handler.codec.SecurityTokenDecoder - Invalid Security Token.

Cause

Action

If a backup does not exist, it is also possible to generate a new security token as per this documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2018

Tags: application server, upgrade, infrastructure, service manager

DRAFT KB-XXXX Unable to start the application server after an upgrade due to invalid security token

Diaba Konate — Wed, 14 Nov 2018 17:10:41 GMT

Revision 1 posted to Appian Knowledge Base by Diaba Konate on 11/14/2018 5:10:41 PM

Symptoms

The application server is unable to start and the following error appears on the application server log:

2018-08-28 13:06:17,248 [Appian PoolManager.CheckInvalidConnections - 4] ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Unexpected exception while handling message for personalization (localhost:5012)
com.appiancorp.kougar.driver.exceptions.TcpException: java.io.EOFException: Socket returned no more data at end of stream

...

com.appiancorp.kougar.driver.exceptions.SafeRetryException: Unable to acquire a Read connection. Safe to retry.
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:154)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:89)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1147)
... 71 more

In service manager log, the following warning is present:

com.appian.komodo.gateway.handler.codec.SecurityTokenDecoder - Invalid Security Token.

Cause

This error appears when the security token has been modified or deleted during the upgrade. In particular, it happen when the security token has been changed after starting Service Manager as the engines will refuse the connection with the application server. The following documentation will provide more details about the security token.

Action

If this occurs during the upgrade, stop all the components and make sure to copy the security token from the backup folder to the new istallation folder. The security token should be in the <APPIAN_HOME>/conf/ folder for Appian version 18.2 and newer or in the <APPIAN_HOME>/ear/suite.ear/conf/ for Appian version 18.1 and previous.

It's also possible to generate a new security token as per this documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2018

Tags: application server, upgrade, service manager

DRAFT KB-XXXX Unable to start the application server after an upgrade due to invalid security token

Diaba Konate — Wed, 14 Nov 2018 12:13:05 GMT

Revision 3 posted to Appian Knowledge Base by Diaba Konate on 11/14/2018 12:13:05 PM

Symptoms

The application server is unable to start and the following error appears on the application server log:

2018-08-28 13:06:17,248 [Appian PoolManager.CheckInvalidConnections - 4] ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Unexpected exception while handling message for personalization (localhost:5012)
com.appiancorp.kougar.driver.exceptions.TcpException: java.io.EOFException: Socket returned no more data at end of stream

...

com.appiancorp.kougar.driver.exceptions.SafeRetryException: Unable to acquire a Read connection. Safe to retry.
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:154)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:89)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1147)
... 71 more

In service manager log, the following warning is present:

com.appian.komodo.gateway.handler.codec.SecurityTokenDecoder - Invalid Security Token.

Cause

Action

If this occurs during the upgrade, stop all the components and make sure to copy the security token from the backup folder to the new installation folder. The security token should be in the <APPIAN_HOME>/conf/ folder for Appian version 18.2 and newer or in the <APPIAN_HOME>/ear/suite.ear/conf/ for Appian version 18.1 and previous.

It's also possible to generate a new security token as per this documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2018

Tags: application server, upgrade, service manager

DRAFT KB-XXXX Unable to start the application server after an upgrade due to invalid security token

Diaba Konate — Wed, 14 Nov 2018 12:12:08 GMT

Revision 2 posted to Appian Knowledge Base by Diaba Konate on 11/14/2018 12:12:08 PM

Symptoms

The application server is unable to start and the following error appears on the application server log:

2018-08-28 13:06:17,248 [Appian PoolManager.CheckInvalidConnections - 4] ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Unexpected exception while handling message for personalization (localhost:5012)
com.appiancorp.kougar.driver.exceptions.TcpException: java.io.EOFException: Socket returned no more data at end of stream

...

com.appiancorp.kougar.driver.exceptions.SafeRetryException: Unable to acquire a Read connection. Safe to retry.
at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:154)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:89)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1147)
... 71 more

In service manager log, the following warning is present:

com.appian.komodo.gateway.handler.codec.SecurityTokenDecoder - Invalid Security Token.

Cause

Action

It's also possible to generate a new security token as per this documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: November 2018

Tags: application server, upgrade, service manager