directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] Commented: (DIRLDAP-74) Launching ADS when it is full of entry is very long
Date Sun, 04 Dec 2005 18:17:30 GMT
    [ ] 

Emmanuel Lecharny commented on DIRLDAP-74:

The previous analyze was plain wrong.

The responsible is org.apache.ldap.server.authz.TupleCache.initialize() which loops through
all the entries :

            Name baseDn = new LdapName( suffix );
            ExprNode filter = new SimpleNode( OC_ATTR, ACSUBENTRY_OC, SimpleNode.EQUALITY
            SearchControls ctls = new SearchControls();
            ctls.setSearchScope( SearchControls.SUBTREE_SCOPE );
            NamingEnumeration results = baseDn, env, filter, ctls );
            while ( results.hasMore() )

This is obviously not a good solution. The TupleCache might be built on the fly, or be serialized
when quitting the server correctly. 

> Launching ADS when it is full of entry is very long
> ---------------------------------------------------
>          Key: DIRLDAP-74
>          URL:
>      Project: Directory LDAP
>         Type: Bug
>     Versions: 0.9.3
>     Reporter: Emmanuel Lecharny
>     Priority: Blocker

> When you launch ApacheDS after having loaded it with thousands of entries, it takes a
while before it can be accessed.
> It seems that all the entries are fetched at launch (all the DN are parsed).
> That does not seems to be reasonnable, as if we have more than a few thousands entries,
it can take ages to start !
> for instance, it takes 21 secondes to start my server with 8155 entries.

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