KB-1685 Appian upgrade results in "403 Forbidden" error on the user interface and "com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself" error in the application server log

Jordan Horwat — Thu, 30 Aug 2018 11:28:43 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 8/30/2018 11:28:43 AM

Symptoms

Users intermittently observe a 403 Forbidden error on the interface after performing an Appian upgrade.

The following error is printed in the application server log located at <JBOSS_HOME>\standalone\log\server.log:

[Appian Work Item - 341 - ProcessExec00 : CatchupRequest] ERROR com.appiancorp.process.engine.CatchupRequest - Failed to register catchup (0), can retry
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) at com.appiancorp.kougar.driver.ipc.IpcConnection.get(IpcConnection.java:390)

The following warning is printed in the db_PX*.log files located at <APPIAN_HOME>\logs\:

[PX011] {pe975.kdb ,1548295} (Default) WARN .a.p.PROCESS.i "Incremental Update: Exec Engine is not ready to start Incremental update.

Cause

The errors indicate that the Appian engine database files did not migrate successfully during the upgrade. One of the likely causes of this issue is an ungraceful shutdown of the Appian engines before the upgrade.

Action

Revert to the backup that was saved before the upgrade and perform the upgrade again following the Update Guide. Ensure the engines are stopped gracefully on the original environment before performing the upgrade again.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

KB-1685 Appian upgrade results in "403 Forbidden" error on the user interface and "com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself" error in the application server log

Jordan Horwat — Thu, 30 Aug 2018 15:26:40 GMT

Revision 17 posted to Appian Knowledge Base by Jordan Horwat on 8/30/2018 3:26:40 PM

Symptoms

Users intermittently observe a 403 Forbidden error on the interface after performing an Appian upgrade.

The following error is printed in the application server log located at <JBOSS_HOME>\standalone\log\server.log:

[Appian Work Item - 341 - ProcessExec00 : CatchupRequest] ERROR com.appiancorp.process.engine.CatchupRequest - Failed to register catchup (0), can retry
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) at com.appiancorp.kougar.driver.ipc.IpcConnection.get(IpcConnection.java:390)

The following error is printed in the db_PX*.log files located at <APPIAN_HOME>\logs\:

[PX011] {pe975.kdb ,1548295} (Default) WARN .a.p.PROCESS.i "Incremental Update: Exec Engine is not ready to start Incremental update.

Cause

The errors indicate that the Appian engine database files did not migrate successfully. One of the likely causes of this issue is an ungraceful shutdown of the Appian engines before the upgrade.

Action

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

DRAFT KB-XXXX Appian upgrade results in "403 Forbidden" error on the user interface and "com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself" error in the application server log

Jordan Horwat — Thu, 30 Aug 2018 11:25:23 GMT

Revision 16 posted to Appian Knowledge Base by Jordan Horwat on 8/30/2018 11:25:23 AM

Symptoms

Users intermittently observe a 403 Forbidden error on the interface after performing an Appian upgrade.

The following error is printed in the application server log located at <JBOSS_HOME>\standalone\log\server.log:

[Appian Work Item - 341 - ProcessExec00 : CatchupRequest] ERROR com.appiancorp.process.engine.CatchupRequest - Failed to register catchup (0), can retry
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) at com.appiancorp.kougar.driver.ipc.IpcConnection.get(IpcConnection.java:390)

The following error is printed in the db_PX*.log files located at <APPIAN_HOME>\logs\:

[PX011] {pe975.kdb ,1548295} (Default) WARN .a.p.PROCESS.i "Incremental Update: Exec Engine is not ready to start Incremental update.

Cause

The errors indicate that the Appian engine database files did not migrate successfully. One of the likely causes of this issue is an ungraceful shutdown of the Appian engines before the upgrade.

Action

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

DRAFT KB-XXXX Appian upgrade results in "403 Forbidden" error on the user interface and "com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself" error in the application server log

Jordan Horwat — Thu, 30 Aug 2018 11:24:49 GMT

Revision 15 posted to Appian Knowledge Base by Jordan Horwat on 8/30/2018 11:24:49 AM

Symptoms

Users intermittently observe a 403 Forbidden error on the interface after performing an Appian upgrade.

The following error is printed in the application server log located at <JBOSS_HOME>\standalone\log\server.log:

[Appian Work Item - 341 - ProcessExec00 : CatchupRequest] ERROR com.appiancorp.process.engine.CatchupRequest - Failed to register catchup (0), can retry
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) at com.appiancorp.kougar.driver.ipc.IpcConnection.get(IpcConnection.java:390)

The following error is printed in the db_PX*.log files located at <APPIAN_HOME>\logs\:

[PX011] {pe975.kdb ,1548295} (Default) WARN .a.p.PROCESS.i "Incremental Update: Exec Engine is not ready to start Incremental update.

Cause

The errors indicate that the Appian engine database files did not migrate successfully. One of the likely causes of this issue is an ungraceful shutdown of the Appian engines before the upgrade.

Action

Revert to the backup that was saved before the migration and perform the migration again following the Update Guide. Ensure the engines are stopped gracefully on the original environment before performing the upgrade again.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

DRAFT KB-XXXX Appian upgrade results in "403 Forbidden" error on the user interface and "com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself" error in the application server log

Jordan Horwat — Thu, 30 Aug 2018 11:24:40 GMT

Revision 14 posted to Appian Knowledge Base by Jordan Horwat on 8/30/2018 11:24:40 AM

Symptoms

Users intermittently observe a 403 Forbidden error on the interface after performing an Appian upgrade.

The following error is printed in the application server log located at <JBOSS_HOME>\standalone\log\server.log:

[Appian Work Item - 341 - ProcessExec00 : CatchupRequest] ERROR com.appiancorp.process.engine.CatchupRequest - Failed to register catchup (0), can retry
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) at com.appiancorp.kougar.driver.ipc.IpcConnection.get(IpcConnection.java:390)

The following error is printed in the db_PX*.log files located at <APPIAN_HOME>\logs\:

[PX011] {pe975.kdb ,1548295} (Default) WARN .a.p.PROCESS.i "Incremental Update: Exec Engine is not ready to start Incremental update.

Cause

The errors indicate that the Appian engine database files did not migrate successfully. One of the likely causes of this issue is an ungraceful shutdown of the Appian engines before the upgrade.

Action

Revert to the backup that was saved before the migration and perform the migration again following Update Guide. Ensure the engines are stopped gracefully on the original environment before performing the upgrade again.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

DRAFT KB-XXXX Appian upgrade results in "403 Forbidden" error on the user interface and "com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself" error in the application server log

Jordan Horwat — Thu, 30 Aug 2018 11:24:15 GMT

Revision 13 posted to Appian Knowledge Base by Jordan Horwat on 8/30/2018 11:24:15 AM

Symptoms

Users intermittently observe a 403 Forbidden error on the interface after performing an Appian upgrade.

The following error is printed in the application server log located at <JBOSS_HOME>\standalone\log\server.log:

[Appian Work Item - 341 - ProcessExec00 : CatchupRequest] ERROR com.appiancorp.process.engine.CatchupRequest - Failed to register catchup (0), can retry
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) at com.appiancorp.kougar.driver.ipc.IpcConnection.get(IpcConnection.java:390)

The following error is printed in the db_PX*.log files located at <APPIAN_HOME>\logs\:

[PX011] {pe975.kdb ,1548295} (Default) WARN .a.p.PROCESS.i "Incremental Update: Exec Engine is not ready to start Incremental update.

Cause

The errors indicate that the Appian engine database files did not migrate successfully. One of the likely causes of this issue is an ungraceful shutdown of the Appian engines before the upgrade.

Action

Revert to the backup that was saved before the migration and perform the migration again as documented in the Update Guide. Ensure the engines are stopped gracefully on the original environment before performing the upgrade again.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

DRAFT KB-XXXX Appian upgrade results in "403 Forbidden" error on the user interface and "com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself" error in the application server log

Jordan Horwat — Thu, 30 Aug 2018 11:22:27 GMT

Revision 12 posted to Appian Knowledge Base by Jordan Horwat on 8/30/2018 11:22:27 AM

Symptoms

Users intermittently observe a 403 Forbidden error on the interface after performing an Appian upgrade.

The following error is printed in the application server log located at <JBOSS_HOME>\standalone\log\server.log:

[Appian Work Item - 341 - ProcessExec00 : CatchupRequest] ERROR com.appiancorp.process.engine.CatchupRequest - Failed to register catchup (0), can retry
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) at com.appiancorp.kougar.driver.ipc.IpcConnection.get(IpcConnection.java:390)

The following error is printed in the db_PX*.log files located at <APPIAN_HOME>\logs\:

[PX011] {pe975.kdb ,1548295} (Default) WARN .a.p.PROCESS.i "Incremental Update: Exec Engine is not ready to start Incremental update.

Cause

The errors indicate that the Appian engine database files did not migrate successfully. One of the likely causes of this issue is an ungraceful shutdown of the Appian engines before the upgrade.

Action

Revert to the backup that was saved before the migration and perform the migration again as documented Update Guide. Ensure the engines are stopped gracefully on the original environment before performing the migration again.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

DRAFT KB-XXXX Appian upgrade results in "403 Forbidden" error on the user interface and "com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself" error in the application server log

Jordan Horwat — Thu, 30 Aug 2018 10:27:16 GMT

Revision 11 posted to Appian Knowledge Base by Jordan Horwat on 8/30/2018 10:27:16 AM

Symptoms

Users intermittently observe a 403 Forbidden error on the interface after performing an Appian upgrade.

The following error is printed in the application server log located at <JBoss_home>\standalone\log\server.log:

[Appian Work Item - 341 - ProcessExec00 : CatchupRequest] ERROR com.appiancorp.process.engine.CatchupRequest - Failed to register catchup (0), can retry
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) at com.appiancorp.kougar.driver.ipc.IpcConnection.get(IpcConnection.java:390)

The following error is printed in the db_PX*.log files located at <APPIAN_HOME>\logs\:

[PX011] {pe975.kdb ,1548295} (Default) WARN .a.p.PROCESS.i "Incremental Update: Exec Engine is not ready to start Incremental update.

Cause

The errors indicate that the Appian engine database files did not migrate successfully. One of the likely causes of this issue is an ungraceful shutdown of the Appian engines before the upgrade.

Action

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

DRAFT KB-XXXX Appian upgrade results in "403 Forbidden" error on the user interface and "com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself" error in the application server log

Jordan Horwat — Thu, 30 Aug 2018 10:26:42 GMT

Revision 10 posted to Appian Knowledge Base by Jordan Horwat on 8/30/2018 10:26:42 AM

Symptoms

Users intermittently observe a 403 Forbidden error on the interface after performing an Appian upgrade.

The following error is printed in the application server log located at <JBoss_home>\standalone\log\server.log:

[Appian Work Item - 341 - ProcessExec00 : CatchupRequest] ERROR com.appiancorp.process.engine.CatchupRequest - Failed to register catchup (0), can retry
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) at com.appiancorp.kougar.driver.ipc.IpcConnection.get(IpcConnection.java:390)

The following error is printed in the db_PX* logs located at <APPIAN_HOME>\logs\:

[PX011] {pe975.kdb ,1548295} (Default) WARN .a.p.PROCESS.i "Incremental Update: Exec Engine is not ready to start Incremental update.

Cause

The errors indicate that the Appian engine database files did not migrate successfully. One of the likely causes of this issue is an ungraceful shutdown of the Appian engines before the upgrade.

Action

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

DRAFT KB-XXXX Appian upgrade results in "403 Forbidden" error seen on the user interface and a "com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself" error seen in the application server log

Jordan Horwat — Thu, 30 Aug 2018 10:18:02 GMT

Revision 9 posted to Appian Knowledge Base by Jordan Horwat on 8/30/2018 10:18:02 AM

Symptoms

Users intermittently observe a '403 Forbidden' error on the interface after performing an Appian upgrade.

The following error is printed in the application server log located at <JBoss_home>\standalone\log\server.log:

[Appian Work Item - 341 - ProcessExec00 : CatchupRequest] ERROR com.appiancorp.process.engine.CatchupRequest - Failed to register catchup (0), can retry
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) at com.appiancorp.kougar.driver.ipc.IpcConnection.get(IpcConnection.java:390)

The following error is printed in the db_PX* logs located at <APPIAN_HOME>\logs\db_PX*.log:

[PX011] {pe975.kdb ,1548295} (Default) WARN .a.p.PROCESS.i "Incremental Update: Exec Engine is not ready to start Incremental update.

Cause

The errors indicate that the Appian Engine Database files did not migrate successfully. One of the likely causes of this issue is due to an ungraceful shutdown of the Appian Engines before the upgrade.

Action

Revert to the backup from before the migration and perform the migration again as documented here. Ensure the engines are stopped gracefully on the original environment before performing the migration.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

DRAFT KB-XXXX Appian upgrade results in "403 Forbidden" error seen on the user interface and a "com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself" error seen in the application server log

Jordan Horwat — Thu, 30 Aug 2018 10:16:54 GMT

Revision 8 posted to Appian Knowledge Base by Jordan Horwat on 8/30/2018 10:16:54 AM

Symptoms

Users intermittently observe a '403 Forbidden' error on the interface after performing an Appian upgrade.

The following error is printed in the application server log located at <JBoss_home>\standalone\log\server.log:

[Appian Work Item - 341 - ProcessExec00 : CatchupRequest] ERROR com.appiancorp.process.engine.CatchupRequest - Failed to register catchup (0), can retry
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) at com.appiancorp.kougar.driver.ipc.IpcConnection.get(IpcConnection.java:390)

The following error is printed in the db_PX* logs located at <Appian_home>\logs\db_PX**:

[PX011] {pe975.kdb ,1548295} (Default) WARN .a.p.PROCESS.i "Incremental Update: Exec Engine is not ready to start Incremental update.

Cause

Action

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

DRAFT KB-XXXX Appian upgrade results in "403 Forbidden" error seen on the user interface and a "com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself" error seen in the application server log

Jordan Horwat — Thu, 30 Aug 2018 10:16:38 GMT

Revision 7 posted to Appian Knowledge Base by Jordan Horwat on 8/30/2018 10:16:38 AM

Symptoms

Users intermittently observe a '403 Forbidden' error on the interface after performing an Appian upgrade.

The following error is printed in the application server log located at <JBoss_home>\standalone\log\server.log:

[Appian Work Item - 341 - ProcessExec00 : CatchupRequest] ERROR com.appiancorp.process.engine.CatchupRequest - Failed to register catchup (0), can retry
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) at com.appiancorp.kougar.driver.ipc.IpcConnection.get(IpcConnection.java:390)

The following error is printed in the db_PX* logs located at <Appian_home>\logs\db_PX**:

[PX011] {pe975.kdb ,1548295} (Default) WARN .a.p.PROCESS.i "Incremental Update: Exec Engine is not ready to start Incremental update.

Cause

Action

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

DRAFT KB-XXXX Appian upgrade results in "403 Forbidden" error seen on the user interface and a "com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself" error seen in the application server log

Tom Ryan — Wed, 29 Aug 2018 20:09:02 GMT

Revision 6 posted to Appian Knowledge Base by Tom Ryan on 8/29/2018 8:09:02 PM

Symptoms

Users intermittently observe a '403 Forbidden' error on the interface after performing an Appian upgrade.

The following error is printed in the application server log located at <JBoss_home>\standalone\log\server.log:

[Appian Work Item - 341 - ProcessExec00 : CatchupRequest] ERROR com.appiancorp.process.engine.CatchupRequest - Failed to register catchup (0), can retry
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) at com.appiancorp.kougar.driver.ipc.IpcConnection.get(IpcConnection.java:390)

The following error is printed in the db_PX* logs located at <Appian_home>\logs\db_PX**:

[PX011] {pe975.kdb ,1548295} (Default) WARN .a.p.PROCESS.i "Incremental Update: Exec Engine is not ready to start Incremental update.

Cause

Action

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

DRAFT KB-XXXX Appian upgrade results in "403 Forbidden" error seen on the user interface and a "com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself" error seen in the application server log

Tejas Kargutkar — Thu, 23 Aug 2018 12:34:20 GMT

Revision 5 posted to Appian Knowledge Base by Tejas Kargutkar on 8/23/2018 12:34:20 PM

Symptoms

Users intermittently observe a '403 Forbidden' error on the interface after performing an Appian upgrade.

The following error is printed in the application server log located at <JBoss_home>\standalone\log\server.log:

[Appian Work Item - 341 - ProcessExec00 : CatchupRequest] ERROR com.appiancorp.process.engine.CatchupRequest - Failed to register catchup (0), can retry
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) at com.appiancorp.kougar.driver.ipc.IpcConnection.get(IpcConnection.java:390)

The following error is printed in the db_PX* logs located at <Appian_home>\logs\db_PX**:

[PX011] {pe975.kdb ,1548295} (Default) WARN .a.p.PROCESS.i "Incremental Update: Exec Engine is not ready to start Incremental update.

Cause

Action

Perform the migration again as documented here and ensure the engines are stopped gracefully on the original environment.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

DRAFT KB-XXXX Appian upgrade results in 403 Errors seen on the user interface with "com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself" error seen in the application server log

Tejas Kargutkar — Wed, 15 Aug 2018 15:46:02 GMT

Revision 4 posted to Appian Knowledge Base by Tejas Kargutkar on 8/15/2018 3:46:02 PM

Symptoms

Users intermittently observe a 403 error on the interface.

An error of the following type is observed in the <JBoss_home>standalone\log\server.log at the same time:

[Appian Work Item - 341 - ProcessExec00 : CatchupRequest] ERROR com.appiancorp.process.engine.CatchupRequest - Failed to register catchup (0), can retry
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) at com.appiancorp.kougar.driver.ipc.IpcConnection.get(IpcConnection.java:390)

<Appian_home>\logs\db_PX** logs have an error of the following type:

[PX011] {pe975.kdb ,1548295} (Default) WARN .a.p.PROCESS.i "Incremental Update: Exec Engine is not ready to start Incremental update.

Cause

The errors indicate that there was an issue with the engine migration. It's possible that the engines were not shutdown gracefully before migrating them.

Action

Perform the migration again as documented here and make sure the engines are stopped gracefully on the original environment.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

Appian upgrade results in 403 Errors seen on the user interface with "com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself" error seen in the application server log

Tejas Kargutkar — Wed, 15 Aug 2018 15:45:24 GMT

Revision 1 posted to Appian Knowledge Base by Tejas Kargutkar on 8/15/2018 3:45:24 PM

Symptoms

Users intermittently observe a 403 error on the interface.

An error of the following type is observed in the server log at the same time:

[Appian Work Item - 341 - ProcessExec00 : CatchupRequest] ERROR com.appiancorp.process.engine.CatchupRequest - Failed to register catchup (0), can retry
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) at com.appiancorp.kougar.driver.ipc.IpcConnection.get(IpcConnection.java:390)

db_PX** logs for the Appian Execution engines, has an error of the following type:
[PX011] {pe975.kdb ,1548295} (Default) WARN .a.p.PROCESS.i "Incremental Update: Exec Engine is not ready to start Incremental update.

Cause

The errors indicate that there was an issue with the engine migration. It's possible that the engines were not shutdown gracefully before migrating them.

Action

Perform the migration again as documented here and make sure the engines are stopped gracefully on the original environment.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

DRAFT KB-XXXX Appian upgrade results in 403 Errors seen on the user interface with "com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself" error seen in the application server log

Tejas Kargutkar — Wed, 15 Aug 2018 12:17:09 GMT

Revision 3 posted to Appian Knowledge Base by Tejas Kargutkar on 8/15/2018 12:17:09 PM

Symptoms

Users intermittently observe a 403 error on the interface.

An error of the following type is observed in the <JBoss_home>standalone\log\server.log at the same time:

[Appian Work Item - 341 - ProcessExec00 : CatchupRequest] ERROR com.appiancorp.process.engine.CatchupRequest - Failed to register catchup (0), can retry
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) at com.appiancorp.kougar.driver.ipc.IpcConnection.get(IpcConnection.java:390)

<Appian_home>\logs\db_PX** logs, have an error of the following type:

[PX011] {pe975.kdb ,1548295} (Default) WARN .a.p.PROCESS.i "Incremental Update: Exec Engine is not ready to start Incremental update.

Cause

The errors indicate that there was an issue with the engine migration. It's possible that the engines were not shutdown gracefully before migrating them.

Action

Perform the migration again as documented here and make sure the engines are stopped gracefully on the original environment.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure

Appian upgrade results in 403 Errors seen on the user interface with "com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself" error seen in the application server log

Tejas Kargutkar — Wed, 15 Aug 2018 11:51:56 GMT

Revision 2 posted to Appian Knowledge Base by Tejas Kargutkar on 8/15/2018 11:51:56 AM

Symptoms

Users intermittently observe a 403 error on the interface.

An error of the following type is observed in the <JBoss_home>standalone\log\server.log at the same time:

[Appian Work Item - 341 - ProcessExec00 : CatchupRequest] ERROR com.appiancorp.process.engine.CatchupRequest - Failed to register catchup (0), can retry
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) com.appiancorp.kougar.driver.exceptions.Signal: Cannot call itself
INFO [stdout] (Appian Work Item - 341 - ProcessExec00 : CatchupRequest) at com.appiancorp.kougar.driver.ipc.IpcConnection.get(IpcConnection.java:390)

<Appian_home>\logs\db_PX** logs, have an error of the following type:

[PX011] {pe975.kdb ,1548295} (Default) WARN .a.p.PROCESS.i "Incremental Update: Exec Engine is not ready to start Incremental update.

Cause

The errors indicate that there was an issue with the engine migration. It's possible that the engines were not shutdown gracefully before migrating them.

Action

Perform the migration again as documented here and make sure the engines are stopped gracefully on the original environment.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2018

Tags: engines, upgrade, infrastructure