Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 80543 invoked from network); 29 Jun 2007 12:58:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 29 Jun 2007 12:58:30 -0000 Received: (qmail 49501 invoked by uid 500); 29 Jun 2007 12:58:30 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 49451 invoked by uid 500); 29 Jun 2007 12:58:29 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 49326 invoked by uid 99); 29 Jun 2007 12:58:29 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Jun 2007 05:58:29 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Jun 2007 05:58:25 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 52F367141E8 for ; Fri, 29 Jun 2007 05:58:05 -0700 (PDT) Message-ID: <5558605.1183121885336.JavaMail.jira@brutus> Date: Fri, 29 Jun 2007 05:58:05 -0700 (PDT) From: "Marcel Reutegger (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Resolved: (JCR-962) Deadlocks in ConcurrentVersioningWithTransactionsTest In-Reply-To: <28394518.1181038886564.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/JCR-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger resolved JCR-962. ---------------------------------- Resolution: Fixed Fix Version/s: 1.4 Assuming lazy consensus I committed the patch in revision: 551877 > Deadlocks in ConcurrentVersioningWithTransactionsTest > ----------------------------------------------------- > > Key: JCR-962 > URL: https://issues.apache.org/jira/browse/JCR-962 > Project: Jackrabbit > Issue Type: Bug > Components: core > Reporter: Bertrand Delacretaz > Fix For: 1.4 > > Attachments: 10-threads-dump.txt, 100-threads-dump.txt, deadlocked-threads.txt, JCR-962-ConcurrentVersioningWithTransactionsTest.patch, JCR-962-fix.patch > > > Patch follows for a ConcurrentVersioningWithTransactionsTest, based on the existing ConcurrentVersioningTest but using transactions around the versioning operations. > On my macbook, running the test with CONCURRENCY = 100 and NUM_OPERATIONS = 100 causes a deadlock after a few seconds, thread dumps follow. > Note that I had to ignore StaleItemStateException (which is probably justified, due to not locking stuff IIUC) to let the threads run long enough to show the problem. > Running the test a few times showed the same locking pattern several times: some threads are locked at line 87 (session.save(), no transaction) while others are at line 93 (transaction.commit()), in testConcurrentCheckinInTransaction(): > 80 public void testConcurrentCheckinInTransaction() throws RepositoryException { > 81 runTask(new Task() { > 82 public void execute(Session session, Node test) throws RepositoryException { > 83 int i = 0; > 84 try { > 85 Node n = test.addNode("test"); > 86 n.addMixin(mixVersionable); > 87 session.save(); > 88 for (i = 0; i < NUM_OPERATIONS / CONCURRENCY; i++) { > 89 final UserTransaction utx = new UserTransactionImpl(test.getSession()); > 90 utx.begin(); > 91 n.checkout(); > 92 n.checkin(); > 93 utx.commit(); > 94 } > 95 n.checkout(); > 96 } catch (Exception e) { > 97 final String threadName = Thread.currentThread().getName(); > 98 final Throwable deepCause = getLevel2Cause(e); > 99 if(deepCause!=null && deepCause instanceof StaleItemStateException) { > 100 // ignore > 101 } else { > 102 throw new RepositoryException(threadName + ", i=" + i + ":" + e.getClass().getName(), e); > 103 } > 104 } > 105 } > 106 }, CONCURRENCY); > 107 } -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.