[ http://issues.apache.org/jira/browse/JCR-443?page=all ]
Tobias Bocanegra closed JCR-443:
--------------------------------
Resolution: Fixed
fixed.
Date: Thu May 25 03:04:54 2006
New Revision: 409351
> Deadlock when concurrently committing and reading versioning states
> -------------------------------------------------------------------
>
> Key: JCR-443
> URL: http://issues.apache.org/jira/browse/JCR-443
> Project: Jackrabbit
> Type: Bug
> Versions: 1.0, 0.9
> Environment: r4093490
> Reporter: Tobias Bocanegra
>
> there is a rear occation when one thread commits a transaction and another
> thread reads versioing related information, so that a deadlock can occurr.
> example:
> Thread1:
> ut.begin();
> session.getWorkspace().clone("default", "/content",
> "/content", true);
> ut.commit();
> Thread2:
> VersionHistory vh = folder.getVersionHistory();
> VersionIterator iter = vh.getAllVersions();
> while (iter.hasNext()) {
> Version v = iter.nextVersion();
> }
> to fix this issue we must ensure, that methods below the shareditemstatemgr
> do not call higher instances (like itemmgr) again.
--
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
