[MAGNOLIA-7037] InvalidItemStateException can occur when trying to remove node with versions Created: 18/May/17 Updated: 06/Mar/19 Resolved: 06/Mar/19 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 5.5 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Jaroslav Simak | Assignee: | Unassigned |
| Resolution: | Workaround exists | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| 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 |
|
javax.jcr.InvalidItemStateException can sometimes occur when calling node.remove() (and most likely also when calling session.removeItem(absPath)). This happens when node has versions, and has pending changes (changes that weren't saved) before calling node.remove() (session.removeItem(absPath)). It's due to removing mixin mgnl:hasVersions from the original node. This call happens when whole version history for the original node is removed. Workaround is easy : save node before removing it. |
| Comments |
| Comment by Richard Gange [ 06/Mar/19 ] |
|
Hi, 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. Best regards, The Magnolia Support Team. |