[JCR-443] Deadlock when concurrently committing and reading versioning states

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.9, 1.0
• Fix Version/s: 1.0.1
• Environment: r4093490
• Assignee: Unassigned
• Reporter: Tobias Bocanegra
• Created: 25/May/06 16:59
• Updated: 26/May/06 17:27
• Resolved: 25/May/06 17:08

Description

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.