From dev-return-30671-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Wed Jul 08 13:33:28 2009 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 54236 invoked from network); 8 Jul 2009 13:33:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 Jul 2009 13:33:28 -0000 Received: (qmail 96613 invoked by uid 500); 8 Jul 2009 13:33:37 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 96317 invoked by uid 500); 8 Jul 2009 13:33:37 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 96146 invoked by uid 99); 8 Jul 2009 13:33:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Jul 2009 13:33:37 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Jul 2009 13:33:35 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id D7C26234C004 for ; Wed, 8 Jul 2009 06:33:14 -0700 (PDT) Message-ID: <125463222.1247059994869.JavaMail.jira@brutus> Date: Wed, 8 Jul 2009 06:33:14 -0700 (PDT) From: "Emmanuel Lecharny (JIRA)" To: dev@directory.apache.org Subject: [jira] Commented: (DIRSERVER-1377) Potential concurrency issue when adding/modifying/deleting entries at a high rate In-Reply-To: <495437817.1245320107339.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DIRSERVER-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728694#action_12728694 ] Emmanuel Lecharny commented on DIRSERVER-1377: ---------------------------------------------- After days of painfull debug sessions, code analysis and log grepping, we have moved the serialization in the backend (JDBM), synchronized correctly JdbmStore, and it seems to have a positive impact. I've run some test, and was able to inject more than 1 400 000 updates without any problem. But the oneLevelIndex is still corrupted, we have to understand why. The idea is to replace the AVLTree by a simple array, which will be sorted. It should be a bit less expensive in CPU, will suck less memory, and cost more for updates. This is what I'm on right now. > Potential concurrency issue when adding/modifying/deleting entries at a high rate > --------------------------------------------------------------------------------- > > Key: DIRSERVER-1377 > URL: https://issues.apache.org/jira/browse/DIRSERVER-1377 > Project: Directory ApacheDS > Issue Type: Bug > Affects Versions: 1.5.4 > Reporter: Emmanuel Lecharny > Priority: Blocker > Fix For: 1.5.5 > > > When adding/deleting entries with many clients (a client add and delete an entry many times), we may have some concurrency problem, as the index are updated without concurrent acces protection. > Synchronizing the classes where we update the index might help. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.