Bug 809777
Summary: | Improvement for the error handling of JCR index build error or node corruption | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Portal Platform 5 | Reporter: | Martin Weiler <mweiler> |
Component: | PicketLink | Assignee: | Boleslaw Dawidowicz <bdawidow> |
Status: | VERIFIED --- | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 5.2.1.GA | CC: | epp-bugs, mposolda, mvecera, theute |
Target Milestone: | --- | Flags: | mvanco:
needinfo-
|
Target Release: | 5.2.2.ER01 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
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.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | Type: | Enhancement | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 830084 | ||
Bug Blocks: |
Description
Martin Weiler
2012-04-04 11:14:40 UTC
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 |