[MAGNOLIA-3188] Upgrade to JackRabbit 1.6.2 (Underlying Apache JackRabbit 1.6.1 bug causes data corruption) Created: 27/Apr/10  Updated: 09/Mar/12  Resolved: 14/Jul/10

Status: Closed
Project: Magnolia
Component/s: activation, build, core
Affects Version/s: 4.3, 4.3.1
Fix Version/s: 4.3.3

Type: Bug Priority: Critical
Reporter: Paul Jara Assignee: Ondrej Chytil
Resolution: Fixed Votes: 0
Labels: activation
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
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   

Apache JackRabbit 1.6.x is claimed to be backwards compatible with previous version. That is not the case and it appears to be leading to severe data corruption issues in our production environment. Specifically, in previous versions of JackRabbit, jcr:isCheckedOut is declared mix:versionable. In the new version it is declared mix:simpleVersionable.

The problem results in some warnings similar to the following:

ItemManager - property at /path/to/node/jcr:isCheckedOut has invalid definitionId (1284956073)

However, it appears to cause activation/deactivation to fail and in at least one case, an activation caused corrupt data to be deployed to the production public instances of our environment causing the entire repository workspace to become corrupt.

The JackRabbit bug has just been declared resolved here (#JCR-2433) https://issues.apache.org/jira/browse/JCR-2433



 Comments   
Comment by Magnolia International [ 20/Oct/10 ]

A belated thank you to Paul for reporting this !

Comment by Daniel Lipp [ 09/Mar/12 ]

Only versions < 4.5 ship with Jackrabbit 1.6.x. 4.5 ships with JackRabbit 2.4 so this issue is not affecting it. Hence 4.5 was removed from "fix versions".

Generated at Mon Feb 12 03:44:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.