Return-Path: X-Original-To: apmail-directory-users-archive@www.apache.org Delivered-To: apmail-directory-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 57907111C3 for ; Sat, 2 Aug 2014 12:25:08 +0000 (UTC) Received: (qmail 3522 invoked by uid 500); 2 Aug 2014 12:25:08 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 3483 invoked by uid 500); 2 Aug 2014 12:25:08 -0000 Mailing-List: contact users-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@directory.apache.org Delivered-To: mailing list users@directory.apache.org Received: (qmail 3469 invoked by uid 99); 2 Aug 2014 12:25:08 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Aug 2014 12:25:07 +0000 Received: from localhost (HELO mail-we0-f172.google.com) (127.0.0.1) (smtp-auth username kayyagari, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Aug 2014 12:25:07 +0000 Received: by mail-we0-f172.google.com with SMTP id x48so5540355wes.31 for ; Sat, 02 Aug 2014 05:25:06 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.74.107 with SMTP id s11mr15710568wiv.68.1406982306121; Sat, 02 Aug 2014 05:25:06 -0700 (PDT) Received: by 10.216.121.68 with HTTP; Sat, 2 Aug 2014 05:25:06 -0700 (PDT) In-Reply-To: References: <53D9EF47.5080802@gmail.com> Date: Sat, 2 Aug 2014 17:55:06 +0530 Message-ID: Subject: Re: [ApacheDS] Entry.next=null, data[removeIndex] Please check that your keys are immutable, and that you have used synchronization properly From: Kiran Ayyagari To: "users@directory.apache.org" Content-Type: multipart/alternative; boundary=f46d0438eb698fce9e04ffa498d9 --f46d0438eb698fce9e04ffa498d9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, Jul 31, 2014 at 4:55 PM, Kiran Ayyagari wrote: > I am able to reproduce this on my dev machine, investigating further > > see https://issues.apache.org/jira/browse/DIRSERVER-1992 for updates > > this is now fixed, please see the bug report for the details. It will be great if anyone of you (David & Brad) can test the latest trunk in your environments. > > On Thu, Jul 31, 2014 at 12:54 PM, Emmanuel L=C3=A9charny > wrote: > >> Crap... >> >> Sounds like we have an issue with the LRUMap we are using to store the >> Entry DN's down into the backend. >> >> Looking at the issue. >> >> >> Can someone create a JIRA for it ? >> >> Many thanks ! >> >> Le 31/07/2014 00:50, Brad a =C3=A9crit : >> > I just ran into this today on version 2.0.0_M17. I am testing concurre= nt >> > queries and sync actions and this happens every time. My record count = is >> > 150K+. >> > >> > "SEARCH_REQUEST >> > Message ID : 1 >> > SearchRequest >> > baseDn : 'ou=3Dcustomers,o=3Dacme.com' >> > filter : '(uid=3D*:[25043])' >> > scope : whole subtree >> > typesOnly : false >> > Size Limit : no limit >> > Time Limit : no limit >> > Deref Aliases : never Deref Aliases >> > attributes : >> > org.apache.directory.api.ldap.model.message.SearchRequestImpl@f95bfade= : >> > Entry.next=3Dnull, data[removeIndex]=3Dnull previous=3Dnull >> key=3D5de68bc6-11ed-4010- >> > 9d48-71f5a54a94a1 value=3Duid=3Dtest@test.com,ou=3Dcustomer,o=3Dacme.c= om >> size=3D10000 >> > maxSize=3D10000 >> > >> > Please check that your keys are immutable, and that you have >> > used synchronization properly. If so, then please report this to >> commons- >> > dev@jakarta.apache.org as a bug..." >> > >> > As described, the server then fails to respond to requests, until >> restart. In >> > this case I am using python's LDAP package and it returns "Other (e.g.= , >> > implementation specific) error'" as the error. >> > >> >> > > > -- > Kiran Ayyagari > http://keydap.com > --=20 Kiran Ayyagari http://keydap.com --f46d0438eb698fce9e04ffa498d9--