directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Zoerner (JIRA)" <>
Subject [jira] Updated: (DIREVE-240) Duplicate root entry gets added everytime restarting the server
Date Wed, 31 Aug 2005 15:31:05 GMT
     [ ]

Stefan Zoerner updated DIREVE-240:

    Attachment: patch_DIREVE-240.txt

Two more comments:
1. The issue exists on the system partition as well.
2. I made a change to the file (patch attached)

The patch adds a conditional to the init method. It checks wether the entry for the suffix
exists. If not, it creates it.
This should remove at least the problem Endi described in this issue (a skilled person shall
check, whether this is a clever change). 

But I am unsure, whether it helps to fix other problems, which may arise if sb changes the
configuration for the partition between startups in the server.xml (e.g. add some attributes
in contextEntry or indexedAttributes  ...).

> Duplicate root entry gets added everytime restarting the server
> ---------------------------------------------------------------
>          Key: DIREVE-240
>          URL:
>      Project: Directory Server
>         Type: Bug
>   Components: jdbm database
>     Versions: 0.9.3
>     Reporter: Endi S. Dewata
>     Assignee: Alex Karasulu
>  Attachments: patch_DIREVE-240.txt
> Duplicate root entry gets added everytime restarting the server.
> Steps to reproduce:
> 1. Start the server:
>     java -jar main/target/apacheds-main-0.9.3-SNAPSHOT.jar main/server.xml
> 2. Use a command line ldapsearch, execute the following:
>     ldapsearch -h localhost -p 10389 -b "dc=apache,dc=org"
>     It returns an entry: dc=apache,dc=org.
> 3. Restart the server.
> 4. Execute the same search operation.
>     This time it returns 2 entries, both are: dc=apache,dc=org.
> The more you restart the server, the more duplicate entries you will get. Note: if you
use an LDAP browser you probably won't see this problem.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message