KB-2230 Processes stuck mid-execution after a hotfix or upgrade for self-managed

Elly Meng — Thu, 05 Jan 2023 22:27:07 GMT

Current Revision posted to Appian Knowledge Base by Elly Meng on 1/5/2023 10:27:07 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After applying a hotfix or upgrading, process models are stuck at the Start Node or after splitting on a gateway node:

Additionally, there are rollback.l files present in the logs directory and the following error is seen in tomcat-stdOut.log:

ERROR com.appiancorp.common.config.ConfigObject - An error occurred while trying to initialize the config LoadExceptionHandling [0ms] [resources 33ms]
java.nio.file.InvalidPathException: Cannot store the note content, because the location is not valid.: /pkgs/appian21.4/_admin/process_notes/exec/00/2/0

Cause

This issue has been hotfixed via AN-198249 in Appian 21.4 and later.

Action

Apply the latest hotfix if on 21.4 or upgrade to 21.4 or later.

Affected Versions

This article applies to self-managed Appian 21.4 and earlier.

Last Reviewed: January 2023

Tags: known issues, installation, fixed issues, processes, infrastructure

KB-2230 Processes stuck mid-execution after a hotfix or upgrade for self-managed

Elly Meng — Thu, 05 Jan 2023 22:27:07 GMT

Revision 6 posted to Appian Knowledge Base by Elly Meng on 1/5/2023 10:27:07 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After applying a hotfix or upgrading, process models are stuck at the Start Node or after splitting on a gateway node:

Additionally, there are rollback.l files present in the logs directory and the following error is seen in tomcat-stdOut.log:

ERROR com.appiancorp.common.config.ConfigObject - An error occurred while trying to initialize the config LoadExceptionHandling [0ms] [resources 33ms]
java.nio.file.InvalidPathException: Cannot store the note content, because the location is not valid.: /pkgs/appian21.4/_admin/process_notes/exec/00/2/0

Cause

This issue has been hotfixed via AN-198249 in Appian 21.4 and later.

Action

Apply the latest hotfix if on 21.4 or upgrade to 21.4 or later.

Affected Versions

This article applies to self-managed Appian 21.4 and earlier.

Last Reviewed: January 2023

Tags: known issues, installation, fixed issues, processes, infrastructure

DRAFT SP-7809 Processes cannot start after an upgrade

Elly Meng — Thu, 05 Jan 2023 22:23:51 GMT

Revision 5 posted to Appian Knowledge Base by Elly Meng on 1/5/2023 10:23:51 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After applying a hotfix or upgrading, process models are stuck at the Start Node or after splitting on a gateway node:

Additionally, there are rollback.l files present in the logs directory and the following error is seen in tomcat-stdOut.log:

ERROR com.appiancorp.common.config.ConfigObject - An error occurred while trying to initialize the config LoadExceptionHandling [0ms] [resources 33ms]
java.nio.file.InvalidPathException: Cannot store the note content, because the location is not valid.: /pkgs/appian21.4/_admin/process_notes/exec/00/2/0

Cause

This issue has been hotfixed via AN-198249 in Appian 21.4 and later.

Action

Apply the latest hotfix if on 21.4 or upgrade to 21.4 or later.

Affected Versions

This article applies to self-managed Appian 21.4 and earlier.

Last Reviewed: January 2023

Tags: known issues, installation, fixed issues, processes, infrastructure

DRAFT SP-7809 Processes cannot start after an upgrade

Elly Meng — Fri, 23 Sep 2022 19:30:28 GMT

Revision 4 posted to Appian Knowledge Base by Elly Meng on 9/23/2022 7:30:28 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After applying a hotfix or upgrading, process models are stuck at the Start Node or after splitting on a gateway node:

Additionally, there are rollback.l files present in the logs directory and the following error is seen in tomcat-stdOut.log:

ERROR com.appiancorp.common.config.ConfigObject - An error occurred while trying to initialize the config LoadExceptionHandling [0ms] [resources 33ms]
java.nio.file.InvalidPathException: Cannot store the note content, because the location is not valid.: /pkgs/appian21.4/_admin/process_notes/exec/00/2/0

Cause

This issue has been hotfixed via AN-198249 in Appian 21.4.425.0 and later.

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Affected Versions

This article applies to self-managed Appian 21.4 and earlier.

Last Reviewed: September 2022

Tags: known issues, installation, fixed issues, processes, infrastructure

DRAFT SP-7809 Processes cannot start after an upgrade

Maggie Deppe-Walker — Mon, 22 Aug 2022 15:13:42 GMT

Revision 3 posted to Appian Knowledge Base by Maggie Deppe-Walker on 8/22/2022 3:13:42 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Process models are stuck at the start node or SPLIT gateway node after applying a hotfix or upgrading Appian. Even simple process models such as the following are stuck:

The following error appears in the tomcat-stdOut.log upon start up:

2022-06-08 20:39:53,544 [ForkJoinPool-1-worker-57] ERROR com.appiancorp.common.config.ConfigObject - An error occurred while trying to initialize the config LoadExceptionHandling [0ms] [resources 33ms]
java.nio.file.InvalidPathException: Cannot store the note content, because the location is not valid.: /pkgs/appian21.4/_admin/process_notes/exec/00/2/0

There are rollback.l files present on the server

Cause

This issue has been hotfixed via AN-198249 in Appian versions 21.4.425.0 and later.

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Affected Versions

This article applies to self-managed Appian 21.4.400.0 and earlier.

Last Reviewed: August 2022

Tags: known issues, installation, fixed issues, processes, infrastructure

DRAFT SP-7809 Processes cannot start after an upgrade

Maggie Deppe-Walker — Thu, 18 Aug 2022 17:09:19 GMT

Revision 2 posted to Appian Knowledge Base by Maggie Deppe-Walker on 8/18/2022 5:09:19 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Process models are stuck at the start node or SPLIT gateway node after applying a hotfix or upgrading Appian. Even simple process models such as the following are stuck:

The following error appears in the tomcat-stdOut.log upon start up:

2022-06-08 20:39:53,544 [ForkJoinPool-1-worker-57] ERROR com.appiancorp.common.config.ConfigObject - An error occurred while trying to initialize the config LoadExceptionHandling [0ms] [resources 33ms]
java.nio.file.InvalidPathException: Cannot store the note content, because the location is not valid.: /pkgs/appian21.4/_admin/process_notes/exec/00/2/0

There are rollback.l files present on the server

Cause

This issue has been hotfixed via AN-198249 in Appian versions 21.4.425.0 and later.

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Affected Versions

This article applies to self-managed Appian 21.4.400.0 and earlier.

Last Reviewed: August 2022

Tags: known issues, installation, fixed issues, processes, infrastructure

DRAFT SP-7809 Processes cannot start after an upgrade

Maggie Deppe-Walker — Thu, 18 Aug 2022 16:55:06 GMT

Revision 1 posted to Appian Knowledge Base by Maggie Deppe-Walker on 8/18/2022 4:55:06 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

Process models are stuck at the start node or SPLIT gateway node after applying a hotfix or upgrading Appian. Even simple process models such as the following are stuck:

The following error appears in the tomcat-stdOut.log upon start up:

ERROR com.appiancorp.common.config.ConfigObject - An error occurred while trying to initialize the config LoadExceptionHandling [0ms] [resources 33ms]
java.nio.file.InvalidPathException: Cannot store the note content, because the location is not valid.: /pkgs/appian21.4/_admin/process_notes/exec/00/2/0
 at com.appiancorp.process.notes.services.NotesContentServiceImpl.createNoteContent(NotesContentServiceImpl.java:164)
 at com.appiancorp.process.notes.services.NotesContentServiceImpl.createNoteContent(NotesContentServiceImpl.java:178)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at com.appiancorp.util.MethodInvocationReflectionImpl.proceed(MethodInvocationReflectionImpl.java:23)
 at com.appiancorp.security.authz.AuthorizationMethodInterceptor.invoke(AuthorizationMethodInterceptor.java:56)
 at com.appiancorp.services.ServiceManager$ServiceInvocationHandler.invoke(ServiceManager.java:479)
 at com.sun.proxy.$Proxy397.createNoteContent(Unknown Source)
 at com.appiancorp.process.execution.service.ExceptionHandlerServiceFacade.registerExceptionTypesWithNotes(ExceptionHandlerServiceFacade.java:160)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at com.appiancorp.util.MethodInvocationReflectionImpl.proceed(MethodInvocationReflectionImpl.java:23)
 at com.appiancorp.security.authz.AuthorizationMethodInterceptor.invoke(AuthorizationMethodInterceptor.java:56)
 at com.appiancorp.services.ServiceManager$ServiceInvocationHandler.invoke(ServiceManager.java:479)
 at com.sun.proxy.$Proxy396.registerExceptionTypesWithNotes(Unknown Source)
 at com.appiancorp.process.admin.LoadExceptionHandling.finish(LoadExceptionHandling.java:56)
 at com.appiancorp.common.config.ConfigObject.runTimed(ConfigObject.java:322)
 at com.appiancorp.common.config.ConfigObject.run(ConfigObject.java:268)
 at com.appiancorp.common.config.ConfigObject.access$100(ConfigObject.java:71)
 at com.appiancorp.common.config.ConfigObject$InitResources.call(ConfigObject.java:253)
 at com.appiancorp.common.config.ConfigObject$InitResources.call(ConfigObject.java:241)
 at java.util.concurrent.ForkJoinTask$AdaptedCallable.exec(ForkJoinTask.java:1424)
 at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
 at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
 at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
 at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:175)

There are rollback.l files present on the server

Cause

This issue has been hotfixed via AN-198249 in Appian versions 21.4.425.0 and later.

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Affected Versions

This article applies to self-managed Appian 21.4.400.0 and earlier.

Last Reviewed: August 2022

Tags: known issues, installation, fixed issues, processes, infrastructure