directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRSERVER-1979) Adding subentries after restarting server, aren't found.
Date Mon, 09 Jun 2014 17:33:04 GMT

    [ https://issues.apache.org/jira/browse/DIRSERVER-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025404#comment-14025404
] 

Emmanuel Lecharny commented on DIRSERVER-1979:
----------------------------------------------

Just to be sure : when you say "subentry", you mean a normal entry added under another one,
or a real LDAP "subentry" ? (ie, an entry with the "objectClass: subentry" attributeType in
it)


> Adding subentries after restarting server, aren't found.
> --------------------------------------------------------
>
>                 Key: DIRSERVER-1979
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1979
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: ldap
>    Affects Versions: 2.0.0-M16, 2.0.0-M17
>         Environment: windows seven.
>            Reporter: Fortunato Margariti
>
> Suppose to have the following situation on the Server (created with ldif):
> dc=xxx,dc=com
> ........ou=groups
> .............. cn=aim
> .............. cn=ais
> .................... cn=aisOperator
> .............. cn=admin
> If you stop and restart the server and then create a subentry (named for example "child")
under any leaf on the tree (in this case under "aim" or "aisOperator" or "admin"), happen
the following:
> 1) the new entry is not visible with a search that start
>  from ou=groups,dc=xxx,dc=com 
> 2) the new entry is visible only if the search start from dc=xxx,dc=com
>    or starting from the leaf: ou=aim,ou=groups,dc=xxx,dc=com
> 3) If you perform an ldif export on ou=groups,dc=xxx,dc=com, you can't find the new added
subentry.
> 4) if the subentry is created under cn=ais (that is not a leaf because has already a
subentry) the new "child" entry is founded by the search
> I was thinking that the problem was related to DIRSERVER-1976 (solved on M17) but we
have the same problems also on this version.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message