[MAGNOLIA-2225] inconsistent workflow state - unable to publish any page Created: 03/Jul/08  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: workflow
Affects Version/s: 3.5.8
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Wolfgang Habicht Assignee: Magnolia International
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnlia 3.5.8, Tomcat 6.0.16, Java 1.6.0_04-b12


Attachments: Text File workflowerror_extracted.log    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Our customer run into the problem, that he could not publish websites anymore.
When publishing a webpage, we got the "normal" textbox that the workflow has been started and the item sent to the inbox.
However, the site never appeared in the inbox.

In the log we found the errors in the attachment

Unfortunately, we do not know how to reproduce the this. But it is obvious that there are some (race?) conditions leading to an inconsistent workflow state.
We fixed the problem in out installation by removing all entries in the store and expressions JCR



 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:34:38 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.