[
https://issues.apache.org/jira/browse/DIRSERVER-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14027550#comment-14027550
]
Kiran Ayyagari commented on DIRSERVER-1979:
-------------------------------------------
The issue is in the RDN index, where the ParentIdAndRdn keys are not replaced
after updating the counts of children and descendants.
I suspect some JDBM cache related issue here, cause for the first 3 entries
injected into the server these counts are properly updated
in the RDN index entry of root context.
As a workaround if I place "rdnIdx.drop( parentId );" at line 938 in
updateRdnIdx() of AbstractBTreePartition the test passes.
> Adding child entries can't be found after restarting server
> -----------------------------------------------------------
>
> 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)
