You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2006/06/02 15:27:30 UTC
[jira] Closed: (JCR-449) inconsistency in internal version items
during commits
[ http://issues.apache.org/jira/browse/JCR-449?page=all ]
Tobias Bocanegra closed JCR-449:
--------------------------------
Resolution: Fixed
quick-fix with some locks in the version manager, but might not be the final/optimal solution. thinking of a coarser restructuration of it.
fixed in revision 411154
> inconsistency in internal version items during commits
> ------------------------------------------------------
>
> Key: JCR-449
> URL: http://issues.apache.org/jira/browse/JCR-449
> Project: Jackrabbit
> Type: Bug
> Versions: 1.0, 1.0.1
> Environment: r410655.
> Reporter: Tobias Bocanegra
> Assignee: Tobias Bocanegra
>
> since some of the versioing information is somehow cached in the 'IternalVersionItems', it can happen that they are not updated fast enough after a commit that included versioning operations. subsequent versioing operations could leed to errors.
> test case: create 2 threads, that concurrently do: begin -> checkout -> checkin -> commit on the same node.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira