[DOCU-1904] Add versioning errors to troubleshooting section Created: 23/Apr/19 Updated: 08/Nov/19 |
|
| Status: | Open |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Low |
| Reporter: | Richard Gange | Assignee: | Richard Gange |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Description |
|
From time to time we get tickets in support referring to versioning issues during publication. For example: 2019-04-18 02:59:54,523 [ERROR] (default task-3) BaseVersionManager - failed to copy versionable node to version store, reverting all changes made in this session javax.jcr.InvalidItemStateException: Node 407aec1e-5241-4be9-98a0-8ab5beb2b810 already exists OR [2019-02-25 09:38:41,768][ERROR] info.magnolia.cms.core.version.BaseVersionManager [ajp-nio-29566-exec-484]: failed to copy versionable node to version store, reverting all changes made in this session javax.jcr.version.VersionException: Unable to perform operation. Node is checked-in. We should create a new page in the Troubleshooting section about these different versioning errors and what steps that should be attempted to solve the problem. Or we could add to the already existing Publishing errors. |