directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kiran Ayyagari (JIRA)" <>
Subject [jira] [Commented] (DIRSERVER-1642) Unexpected behaviour in JdbmIndex
Date Tue, 16 Aug 2011 20:48:27 GMT


Kiran Ayyagari commented on DIRSERVER-1642:

I have recently discussed this sort of behavior with Emmanuel while trying to consider JDBM
for replication journal.
The javadoc of browse() method in BTree says:

 WARNING: If you make structural modifications to the BTree during browsing, you will get
inconsistent browing results.

> Unexpected behaviour in JdbmIndex
> ---------------------------------
>                 Key: DIRSERVER-1642
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Bug
>            Reporter: Stefan Seelmann
>         Attachments:
> During my experiments and tests of removing one-level and sub-level indices at least
one integration test "SearchAuthorizationIT" failed (the test fails recursivelyDelete()).
A debugging session showed that the follwing:
> - in recursivelyDelete() multiple search requests are done which leads to multiple open
cursors in the XDBM search engine
> - an entry is deleted
> - when the open cursors are advanced wrong/unexpected entries are returned
> I was able to create a small test that shows the problem:
> - the index contains six tuples:
> (a,1)
> (b,2)
> (c,3)
> (d,4)
> (e,5)
> (f,6)
> - a cursor over the index is created and advanced two times, the expected tuples (a,1)
and (b,2) were returned
> - now tuple (c,3) is deleted
> - when the cursor is advanced again the tuple (b,2) is returned again! I had expected
> Note that this doesn't happen with AvlIndex.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message