From dev-return-30616-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Wed Jun 17 23:03:51 2009 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 40594 invoked from network); 17 Jun 2009 23:03:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Jun 2009 23:03:51 -0000 Received: (qmail 75267 invoked by uid 500); 17 Jun 2009 23:04:02 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 75181 invoked by uid 500); 17 Jun 2009 23:04:01 -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 75173 invoked by uid 99); 17 Jun 2009 23:04:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jun 2009 23:04:01 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of akarasulu@gmail.com designates 209.85.217.214 as permitted sender) Received: from [209.85.217.214] (HELO mail-gx0-f214.google.com) (209.85.217.214) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jun 2009 23:03:51 +0000 Received: by gxk10 with SMTP id 10so1051667gxk.1 for ; Wed, 17 Jun 2009 16:03:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=/rJ3oFxESOI4T36sXztRwTFh76PtpX+VMCGyorlDxt0=; b=LBpVxRwN9WVjRie5P5eyKFteKrspjSZmeZs8BtvDUffNjoiJFkd0qlBd4nnyNDJYye smNMYp0rh9XPnbvkmiuf2axS4DYhUnudC6QWpvhHHMa7paYPM8nHcJRtVXRlP6QdkW9n HnvzXRW+QuBXJao2Nou7gIayVoZZJlSBvXkxc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=tkIoaoBbcuO0Pka2IxKvYIKRvNjSivra6vIhITjABpjSqJf0hSk1zxtBiphCHngd/t 2FB1LiItryF4hQoClZwgkptxJwTQtm2Q81kMg+O1kToYePJ5FPyLQjv9xwWVWW8h7Bqb i/VDCxBFWnat5KrRT2SZJflpSvcMFm/nOq+3Q= MIME-Version: 1.0 Received: by 10.231.39.130 with SMTP id g2mr269498ibe.9.1245279810554; Wed, 17 Jun 2009 16:03:30 -0700 (PDT) In-Reply-To: <4A396D69.7060409@nextury.com> References: <5A2110DC1CD00B45A0832E5BF98ECB0602BC9E604C@ex2> <5A2110DC1CD00B45A0832E5BF98ECB0602CFB24D41@ex2> <4A396D69.7060409@nextury.com> Date: Wed, 17 Jun 2009 19:03:30 -0400 Message-ID: Subject: Re: [ApacheDS] [JDBM] Index .db files grow from attribute replace From: Alex Karasulu To: Apache Directory Developers List Content-Type: multipart/alternative; boundary=00032557492ac10b19046c934cf8 X-Virus-Checked: Checked by ClamAV on apache.org --00032557492ac10b19046c934cf8 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable The problem with holes and a lack of defragmentation worries me with JDBM. I wish we had some tools to correct these issues like the ones that come with JE. On Wed, Jun 17, 2009 at 6:25 PM, Emmanuel Lecharny wr= ote: > Martin Alderson wrote: > >> I've found the problem with this now. >> >> It seems to be a bug within JDBM 1.0. This was fixed in JDBMs CVS >> repository back in February last year - before we branched: >> http://jdbm.cvs.sourceforge.net/viewvc/jdbm/jdbm/src/main/jdbm/btree/BTr= ee.java?r1=3D1.17&r2=3D1.18 >> >> I guess we just branched the 1.0 code. Can we just go ahead and apply >> this patch or should we sync up with the latest JDBM trunk? >> >> Thanks, >> >> > > Sorry for the late (!!!) answer. The patch has been applied a long time > ago. > > We just have fixed another issue with index : DIRSERVER-1376 > > -- > -- > cordialement, regards, > Emmanuel L=E9charny > www.iktek.com > directory.apache.org > > > --=20 Alex Karasulu My Blog :: http://www.jroller.com/akarasulu/ Apache Directory Server :: http://directory.apache.org Apache MINA :: http://mina.apache.org --00032557492ac10b19046c934cf8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable The problem with holes and a lack of defragmentation worries me with JDBM.= =A0 I wish we had some tools to correct these issues like the ones that com= e with JE.=A0

On Wed, Jun 17, 2009 at 6:= 25 PM, Emmanuel Lecharny <elecharny@apache.org> wrote:
Martin Alderson w= rote:
I've found the problem with this now.

It seems to be a bug within JDBM 1.0. =A0This was fixed in JDBMs CVS reposi= tory back in February last year - before we branched: http://jdbm.cvs.sourceforge.net/viewv= c/jdbm/jdbm/src/main/jdbm/btree/BTree.java?r1=3D1.17&r2=3D1.18

I guess we just branched the 1.0 code. =A0Can we just go ahead and apply th= is patch or should we sync up with the latest JDBM trunk?

Thanks,
=A0

Sorry for the late (!!!) answer. The patch has been applied a long time ago= .

We just have fixed another issue with index : DIRSERVER-1376

--
--
cordialement, regards,
Emmanuel L=E9charny
www.iktek.com
directory.apache.= org





--
Alex KarasuluMy Blog :: http://www.jrolle= r.com/akarasulu/
Apache Directory Server :: http://directory.apache.org
Apache MINA :: http://mina.apache.org

--00032557492ac10b19046c934cf8--