Magnolia 5.7 reached extended end of life on May 31, 2022. Support for this branch is limited, see End-of-life policy. Please note that to cover the extra maintenance effort, this EEoL period is a paid extension in the life of the branch. Customers who opt for the extended maintenance will need a new license key to run future versions of Magnolia 5.7. If you have any questions or to subscribe to the extended maintenance, please get in touch with your local contact at Magnolia.
Inconsistent version history can cause problems in Magnolia whenever you need to work with a past version of a node.
If a version history is broken, you see the exception
org.apache.jackrabbit.core.state.NoSuchItemStateException in the log files.
To fix these types of issues you can use the system parameter:
To use the parameter, do the following:
- Stop Magnolia.
Add the JVM parameter:
- Start Magnolia.
Disable the JVM parameter once you have recovered from a corrupted version history. After recovery, there is no benefit to keeping the property enabled and leaving it enabled can have serious side effects, for example:
- Deploying a new webapp to a JVM that has the property enabled can prevent the repository initializing correctly.
- When enabled, the property delays startup times significantly.