Description of problem: Sometimes we face JCR index build error or node corruption during EPP/SP startup. Is it possible to improve the error handling so that EPP can startup and still serve contents ignoring bad index/corrupted nodes? It's important for availability of enterprise portal sites. Version-Release number of selected component (if applicable): eXo JCR 1.14.3 How reproducible: Sometimes when the EPP cluster breaks, this results in JCR data corruption. Actual results: EPP fails to start. Expected results: EPP can start, and just log the data corruption Additional info: Depends on upgrade of eXo JCR
Should be fixed once EPP includes eXo JCR 1.14.7, 1.15.0 or higher.
Martin, JCR 1.14.8-CR01 was included in EPP 5.2.2 ER02 and 1.14.8-C0R2 is expected in next release cycle. Can you please provide more information how this can be verified or if JCR update is enough? Thanks
This is fixed by updated JCR component, related jira was https://issues.jboss.org/browse/EXOJCR-1778, confirmed by Martin.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: If JCR index is broken, JCR stops. Consequence: Sometimes we face JCR index build error or node corruption during EPP/SP startup. Fix: Upgrade JCR Result: EPP can start, and just log the data corruption
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,7 +1 @@ -Cause: If JCR index is broken, JCR stops. +It was discovered that if the JCR index is broken, JCR stops. This caused a JCR index build error or node corruption during portal and Site Publisher start-up. The fix includes upgrades to the JCR which allows the portal to start correctly and log the data corruption, rather instead of failing to start.- -Consequence: Sometimes we face JCR index build error or node corruption during EPP/SP startup. - -Fix: Upgrade JCR - -Result: EPP can start, and just log the data corruption
Verified again at 5.2.2 CR01
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.