Return-Path: Delivered-To: apmail-incubator-jackrabbit-dev-archive@www.apache.org Received: (qmail 64947 invoked from network); 10 Nov 2004 21:30:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 10 Nov 2004 21:30:27 -0000 Received: (qmail 13379 invoked by uid 500); 10 Nov 2004 21:30:25 -0000 Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jackrabbit-dev@incubator.apache.org Delivered-To: mailing list jackrabbit-dev@incubator.apache.org Received: (qmail 13366 invoked by uid 99); 10 Nov 2004 21:30:25 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10) by apache.org (qpsmtpd/0.28) with SMTP; Wed, 10 Nov 2004 13:30:25 -0800 Received: (qmail 2820 invoked from network); 10 Nov 2004 21:30:23 -0000 Received: from localhost (HELO nagoya) (127.0.0.1) by nagoya.betaversion.org with SMTP; 10 Nov 2004 21:30:23 -0000 Message-ID: <754032452.1100122223788.JavaMail.apache@nagoya> Date: Wed, 10 Nov 2004 13:30:23 -0800 (PST) From: "Felix Meschberger (JIRA)" To: jackrabbit-dev@incubator.apache.org Subject: [jira] Created: (JCR-18) Multithreading issue with versioning Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Multithreading issue with versioning ------------------------------------ Key: JCR-18 URL: http://nagoya.apache.org/jira/browse/JCR-18 Project: Jackrabbit Type: Bug Environment: Jackrabbit SVN Rev. 56918 Reporter: Felix Meschberger 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. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira