Error:javax.jcr.PathNotFoundException: /etc/workflow/instances/server0/2017-10-01/wso-2choice-final_159 | Community
Skip to main content
V
Venkata_B
Level 2
September 12, 2018
Solved

Error:javax.jcr.PathNotFoundException: /etc/workflow/instances/server0/2017-10-01/wso-2choice-final_159

  • September 12, 2018
  • 1 reply
  • 1637 views

We have recently upgraded form AEM 6.1 to AEM 6.3. Before upgrading, we didnt purge the workflow instances. After the upgrade, we see errors in the logs where it is unable to find  a specific node /etc/workflow/instances/server0/2017-10-01/wso-2choice-final_159. The node doesnt exist in AEM 6.3 anymore. However, I see that node on AEM 6.1.

I want to resolve the error in my logs "Caused by: javax.jcr.PathNotFoundException: /etc/workflow/instances/server0/2017-10-01/wso-2choice-final_159"

What can I do to resolve the problems?

Any help is greatly appreciated.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by arunpatidar

Hi,

Whenever you create workflow to publish page/assets, one instance is created for each workflow like /etc/workflow/instances/server0/2017-10-01/wso-2choice-final_159

This workflow instance represents the state of workflow, transitions, payload etc and inbox notification are also triggered for each instance.

This error is triggered(by resource-status http://localhost:4502/resource-status/editor/content/AEM63App/fr.1.json?_=1536844386443 ) when you access a page which was part of incomplete workflow and instance is deleted/or not available.

You may package those incomplete instance and install at new instance terminate the workflow to avoid this exceptions.


1 reply

arunpatidar
Community Advisor
arunpatidarCommunity AdvisorAccepted solution
Community Advisor
September 13, 2018

Hi,

Whenever you create workflow to publish page/assets, one instance is created for each workflow like /etc/workflow/instances/server0/2017-10-01/wso-2choice-final_159

This workflow instance represents the state of workflow, transitions, payload etc and inbox notification are also triggered for each instance.

This error is triggered(by resource-status http://localhost:4502/resource-status/editor/content/AEM63App/fr.1.json?_=1536844386443 ) when you access a page which was part of incomplete workflow and instance is deleted/or not available.

You may package those incomplete instance and install at new instance terminate the workflow to avoid this exceptions.


Arun Patidar
Terms & ConditionsAccessibility statement

Loading footer...