[#JCR-18] Multithreading issue with versioning

Jackrabbit Content Repository

Multithreading issue with versioning

Created: 10/Nov/04 09:27 PM Updated: 08/Oct/07 10:47 AM

Return to search

Component/s:

versioning

Affects Version/s:

0.9, 1.0, 1.0.1, 1.1, 1.1.1, 1.2.1, 1.2.2, 1.2.3, 1.3, 1.3.1

Fix Version/s:

1.3.3

Time Tracking:

Not Specified

Environment:

Jackrabbit SVN Rev. 56918

Issue Links:

Reference

This issue relates to:

~~JCR-754~~ Exception when concurrently adding nodes with JCA and XA transactions

~~JCR-140~~ Versioning might no be thread safe

This issue is related to:

~~JCR-962~~ Deadlocks in ConcurrentVersioningWithTransactionsTest

~~JCR-790~~ Possible deadlock during concurrent operations on versionable nodes

Resolution Date:

26/Jun/07 08:01 AM

Description

« Hide

In a multithreading environment with two or more threads accessing the same version history, inconsistent state may be encountered. Concretely, the first thread is currently checking in the node to which the version history is attached while the second thread walks this same version history by means of a "self-built" iterator, which just accesses the successors of each version to get the "next" to visit.

At a certain point the second point may encounter an ItemNotFoundException with a stack trace similar to this:

javax.jcr.ItemNotFoundException: c9bd405b-dff4-46ef-845c-d98e073e473a
        at org.apache.jackrabbit.core.ItemManager.createItemInstance(ItemManager.java:354)
        at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:230)
        at org.apache.jackrabbit.core.SessionImpl.getNodeByUUID(SessionImpl.java:494)
        at org.apache.jackrabbit.core.version.VersionImpl.getSuccessors(VersionImpl.java:86)
        ....

It seems that the first thread has already filled the successor of the version, while the node is not yet accessible by the createItemInstance method.

This bug seems to not be enforcible, but it is easily reproducible.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

Tobias Bocanegra made changes - 11/Nov/04 02:42 PM

Field	Original Value	New Value
Assignee		Tobias Strasser [ tripod ]

Tobias Bocanegra made changes - 17/Nov/04 10:02 AM

Resolution		Fixed [ 1 ]
Status	Open [ 1 ]	Resolved [ 5 ]

Tobias Bocanegra made changes - 19/Nov/04 02:46 PM

Resolution	Fixed [ 1 ]
Status	Resolved [ 5 ]	Reopened [ 4 ]

Roy T. Fielding made changes - 13/Mar/05 04:45 AM

Component/s

versioning [ 11612 ]

Jukka Zitting made changes - 30/Jun/05 11:10 PM

Description	In a multithreading environment with two or more threads accessing the same version history, inconsistent state may be encountered. Concretely, the first thread is currently checking in the node to which the version history is attached while the second thread walks this same version history by means of a "self-built" iterator, which just accesses the successors of each version to get the "next" to visit. At a certain point the second point may encounter an ItemNotFoundException with a stack trace similar to this: javax.jcr.ItemNotFoundException: c9bd405b-dff4-46ef-845c-d98e073e473a at org.apache.jackrabbit.core.ItemManager.createItemInstance(ItemManager.java:354) at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:230) at org.apache.jackrabbit.core.SessionImpl.getNodeByUUID(SessionImpl.java:494) at org.apache.jackrabbit.core.version.VersionImpl.getSuccessors(VersionImpl.java:86) .... It seems that the first thread has already filled the successor of the version, while the node is not yet accessible by the createItemInstance method. This bug seems to not be enforcible, but it is easily reproducible.	In a multithreading environment with two or more threads accessing the same version history, inconsistent state may be encountered. Concretely, the first thread is currently checking in the node to which the version history is attached while the second thread walks this same version history by means of a "self-built" iterator, which just accesses the successors of each version to get the "next" to visit. At a certain point the second point may encounter an ItemNotFoundException with a stack trace similar to this: javax.jcr.ItemNotFoundException: c9bd405b-dff4-46ef-845c-d98e073e473a at org.apache.jackrabbit.core.ItemManager.createItemInstance(ItemManager.java:354) at org.apache.jackrabbit.core.ItemManager.getItem(ItemManager.java:230) at org.apache.jackrabbit.core.SessionImpl.getNodeByUUID(SessionImpl.java:494) at org.apache.jackrabbit.core.version.VersionImpl.getSuccessors(VersionImpl.java:86) .... It seems that the first thread has already filled the successor of the version, while the node is not yet accessible by the createItemInstance method. This bug seems to not be enforcible, but it is easily reproducible.
Fix Version/s		1.0 [ 12310154 ]

Jukka Zitting made changes - 30/Jun/05 11:14 PM

Link

This issue relates to ~~JCR-140~~ [ ~~JCR-140~~ ]

Jukka Zitting made changes - 07/Mar/06 03:32 PM

Fix Version/s	1.0 [ 12310154 ]
Fix Version/s		1.1 [ 12310346 ]

Jukka Zitting made changes - 21/Mar/06 06:26 AM

Affects Version/s		1.0 [ 12310154 ]
Affects Version/s		0.9 [ 12310719 ]

Jukka Zitting made changes - 17/Sep/06 10:04 PM

Fix Version/s

1.1 [ 12310346 ]

Stefan Guggisberg made changes - 21/Feb/07 01:26 PM

Link

This issue relates to ~~JCR-754~~ [ ~~JCR-754~~ ]

Stefan Guggisberg made changes - 14/Mar/07 12:11 PM

Link

This issue is related to ~~JCR-790~~ [ ~~JCR-790~~ ]

Bertrand Delacretaz made changes - 05/Jun/07 10:29 AM

Link

This issue is related to ~~JCR-962~~ [ ~~JCR-962~~ ]

Jukka Zitting made changes - 25/Jun/07 02:36 PM

Comment

[ This seems to be related to ~~JCR-18~~ ]

Marcel Reutegger made changes - 26/Jun/07 08:01 AM

Status	Reopened [ 4 ]	Resolved [ 5 ]
Fix Version/s		1.4 [ 12312447 ]
Resolution		Fixed [ 1 ]

Jukka Zitting made changes - 20/Jul/07 09:10 PM

Affects Version/s		1.1.1 [ 12312099 ]
Affects Version/s		1.3.1 [ 12312512 ]
Affects Version/s		1.2.1 [ 12312100 ]
Affects Version/s		1.1 [ 12310346 ]
Affects Version/s		1.2.3 [ 12312329 ]
Affects Version/s		1.3 [ 12312229 ]
Affects Version/s		1.2.2 [ 12312228 ]
Affects Version/s		1.0.1 [ 12310345 ]

Jukka Zitting made changes - 02/Oct/07 10:03 AM

Fix Version/s	1.4 [ 12312447 ]
Fix Version/s		1.3.2 [ 12312770 ]

Jukka Zitting made changes - 08/Oct/07 10:47 AM

Status

Resolved [ 5 ]

Closed [ 6 ]

Jukka Zitting made changes - 07/Jul/09 01:03 PM

Workflow

jira [ 38320 ]

no-reopen-closed, patch-avail [ 12468905 ]