[JCR-2290] Potential concurrency issues of Workspace operations

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: jackrabbit-core
• Assignee: Unassigned
• Reporter: Stefan Guggisberg
• Created: 02/Sep/09 15:59
• Updated: 22/Feb/10 09:00

Description

while investigating JCR-2269 i discovered that the following javax.jcr.Workspace operations are affected by potential concurency issues:

copy
clone
move
importXML
getImportContentHandler

those operations directly operate on ItemState instances returned from LocalItemStateManager (LISM).
typically a workspace operation gets an ItemState instance from the LISM, does some validations,
modifies the state and finally stores it in the ChangeLog for further processing.

the problem is that the local ItemState instance is not isolated from external changes, i.e. it might change
at any point (e.g. after validation) due to external underlying changes. only when it is stored in the
ChangeLog it is disconnected from its underlying state.

Issue Links

• relates to: JCR-2503 inconsistent session and persistent state after ReferentialIntegrityException