[
https://issues.apache.org/jira/browse/JCR-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved JCR-2960.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.3.0
Ouch, good catch! Fixed in revision 1100286 along with tests also for some
other value types.
Luckily this is not a serialization bug so none of the stored data itself is
compromized unless used as input for copies or further calculations. However,
we'll need to backport this fix to the 2.2 branch and warn people not to rely
on large values read from the repository until this fix has been applied. I'll
take care of that first thing next week.
> Long values not properly stored
> -------------------------------
>
> Key: JCR-2960
> URL: https://issues.apache.org/jira/browse/JCR-2960
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.2.0, 2.2.1, 2.2.4, 2.2.5
> Reporter: Antoine Brochard
> Assignee: Jukka Zitting
> Priority: Critical
> Fix For: 2.3.0
>
> Attachments: LongValueTest.java
>
>
> When a long value assigned to a property is too big, when restarting the
> server the value become 0 !!
> The test pass with versions 1.6.4 and 2.0
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
