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] Updated: (DIRSERVER-1010) Should the order in which hot partitions are connected to matter?
Date Fri, 24 Aug 2007 13:01:34 GMT

     [ https://issues.apache.org/jira/browse/DIRSERVER-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Emmanuel Lecharny updated DIRSERVER-1010:
-----------------------------------------

    Affects Version/s: 1.5.0
        Fix Version/s: 1.5.2

Added Affect/Fix infos (please do add the affect version when filling a JIRA, this helps a
lot !)

To be further investigated after the next release (1.5.1), so postponed.

> Should the order in which hot partitions are connected to matter?
> -----------------------------------------------------------------
>
>                 Key: DIRSERVER-1010
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1010
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.5.0
>            Reporter: Ole Ersoy
>             Fix For: 1.5.2
>
>
> If I connect in this order:
>         dasContext = 
>             adsEmbeddedConnection.
>             connect( 
>                 configuration.getDasPartitionName() );
>         schemaContext = 
>             adsEmbeddedConnection.
>             connect( 
>                 configuration.getSchemaPartitionName() );
> I don't get any exceptions.
> If I flip the two, I get this exception:
> org.apache.directory.shared.ldap.exception.LdapNameNotFoundException: ou=das
> 	at org.apache.directory.server.core.partition.DefaultPartitionNexus.getBackend(DefaultPartitionNexus.java:1064)
> 	at org.apache.directory.server.core.partition.DefaultPartitionNexus.hasEntry(DefaultPartitionNexus.java:988)
> 	at org.apache.directory.server.core.interceptor.InterceptorChain$1.hasEntry(InterceptorChain.java:147)
> 	at org.apache.directory.server.core.interceptor.InterceptorChain$Entry$1.hasEntry(InterceptorChain.java:1246)
> 	at org.apache.directory.server.core.interceptor.BaseInterceptor.hasEntry(BaseInterceptor.java:130)
> 	at org.apache.directory.server.core.interceptor.InterceptorChain$Entry$1.hasEntry(InterceptorChain.java:1246)
> 	at org.apache.directory.server.core.interceptor.BaseInterceptor.hasEntry(BaseInterceptor.java:130)
> .....
> I'll check in the working DAS in a few days and in the package:
> package org.apache.tuscany.das.ldap.emf.test;
> There is a test called LdapDASHelperTest that can be run to see this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message