You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@directory.apache.org by Kiran Ayyagari <ka...@apache.org> on 2014/07/24 20:25:33 UTC
Re: [ApacheDS] Entry.next=null, data[removeIndex] Please check that
your keys are immutable, and that you have used synchronization properly
David,
which version of the server are you using? I have fixed some stale cache
issues in a very old milestone
release (2.0.0-M5 or M6) and since then never encountered any cache
related issues so far.
On Wed, Jul 23, 2014 at 11:57 PM, Foust, David M. (MSFC-IS80)[EAST] <
david.foust@nasa.gov> wrote:
> Hello, I'm having a strange issue where I find that I cannot query the
> LDAP after a large synchronization operation that occurs at night. The sync
> deletes and recreates about 25,000 entries with an average of 30 attributes
> each. Each entry is a separate call to ldapmodify. This condition is
> 'corrected' by restarting the ldap server. This makes me suspect it is a
> cache corruption of some sort. I'm not getting anything in the log on the
> server, this error is client side only. I've tried adjusting cache from
> 100,000 to 1,000 entries for the partition, as well as enabling and
> disabling write sync. The JVM is 1 GB xmx.
>
> 10:28:04 AM: List failed
> Root error: [LDAP: error code 1 - OPERATIONS_ERROR: failed for MessageType
> : SEARCH_REQUEST
> Message ID : 2
> SearchRequest
> baseDn : ''
> filter : '(objectClass=*)'
> scope : single level
> typesOnly : false
> Size Limit : no limit
> Time Limit : no limit
> Deref Aliases : never Deref Aliases
> attributes : 'numsubordinates'
> org.apache.directory.api.ldap.model.message.SearchRequestImpl@5f3340d2:
> Entry.next=null,
> data[removeIndex]=85bf738a-38c6-48c8-8772-1d000695d730=employeenumber=0000ntvd177,ou=People,dc=nasa,dc=gov
> previous=3a39fa31-9a7a-4b41-bf09-d356b8258a7b=employeenumber=13584685,ou=People,dc=nasa,dc=gov
> key=da6930c8-7524-488e-9e29-c1fb92c4f13d value=dc=nasa,dc=gov size=10000
> maxSize=10000 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<ma...@jakarta.apache.org> as
> a bug.]
>
> Any assistance is much appreciated!
>
> David
>
>
--
Kiran Ayyagari
http://keydap.com
Re: [ApacheDS] Entry.next=null, data[removeIndex] Please check that
your keys are immutable, and that you have used synchronization properly
Posted by Kiran Ayyagari <ka...@apache.org>.
On Thu, Jul 31, 2014 at 4:55 PM, Kiran Ayyagari <ka...@apache.org>
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écharny <el...@gmail.com>
> 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 écrit :
>> > I just ran into this today on version 2.0.0_M17. I am testing concurrent
>> > queries and sync actions and this happens every time. My record count is
>> > 150K+.
>> >
>> > "SEARCH_REQUEST
>> > Message ID : 1
>> > SearchRequest
>> > baseDn : 'ou=customers,o=acme.com'
>> > filter : '(uid=*:[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=null, data[removeIndex]=null previous=null
>> key=5de68bc6-11ed-4010-
>> > 9d48-71f5a54a94a1 value=uid=test@test.com,ou=customer,o=acme.com
>> size=10000
>> > maxSize=10000
>> >
>> > 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
>
--
Kiran Ayyagari
http://keydap.com
Re: [ApacheDS] Entry.next=null, data[removeIndex] Please check that
your keys are immutable, and that you have used synchronization properly
Posted by Kiran Ayyagari <ka...@apache.org>.
I am able to reproduce this on my dev machine, investigating further
see https://issues.apache.org/jira/browse/DIRSERVER-1992 for updates
On Thu, Jul 31, 2014 at 12:54 PM, Emmanuel Lécharny <el...@gmail.com>
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 écrit :
> > I just ran into this today on version 2.0.0_M17. I am testing concurrent
> > queries and sync actions and this happens every time. My record count is
> > 150K+.
> >
> > "SEARCH_REQUEST
> > Message ID : 1
> > SearchRequest
> > baseDn : 'ou=customers,o=acme.com'
> > filter : '(uid=*:[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=null, data[removeIndex]=null previous=null
> key=5de68bc6-11ed-4010-
> > 9d48-71f5a54a94a1 value=uid=test@test.com,ou=customer,o=acme.com
> size=10000
> > maxSize=10000
> >
> > 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
Re: [ApacheDS] Entry.next=null, data[removeIndex] Please check that
your keys are immutable, and that you have used synchronization properly
Posted by Emmanuel Lécharny <el...@gmail.com>.
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 écrit :
> I just ran into this today on version 2.0.0_M17. I am testing concurrent
> queries and sync actions and this happens every time. My record count is
> 150K+.
>
> "SEARCH_REQUEST
> Message ID : 1
> SearchRequest
> baseDn : 'ou=customers,o=acme.com'
> filter : '(uid=*:[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=null, data[removeIndex]=null previous=null key=5de68bc6-11ed-4010-
> 9d48-71f5a54a94a1 value=uid=test@test.com,ou=customer,o=acme.com size=10000
> maxSize=10000
>
> 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.
>
Re: [ApacheDS] Entry.next=null, data[removeIndex] Please check that your keys are immutable, and that you have used synchronization properly
Posted by Brad <bj...@gmail.com>.
I just ran into this today on version 2.0.0_M17. I am testing concurrent
queries and sync actions and this happens every time. My record count is
150K+.
"SEARCH_REQUEST
Message ID : 1
SearchRequest
baseDn : 'ou=customers,o=acme.com'
filter : '(uid=*:[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=null, data[removeIndex]=null previous=null key=5de68bc6-11ed-4010-
9d48-71f5a54a94a1 value=uid=test@test.com,ou=customer,o=acme.com size=10000
maxSize=10000
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.