Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 23031 invoked from network); 26 Jul 2007 21:00:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Jul 2007 21:00:32 -0000 Received: (qmail 62675 invoked by uid 500); 26 Jul 2007 21:00:30 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 62544 invoked by uid 500); 26 Jul 2007 21:00:29 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 62508 invoked by uid 99); 26 Jul 2007 21:00:29 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jul 2007 14:00:29 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jul 2007 14:00:27 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id A561C7141F2 for ; Thu, 26 Jul 2007 14:00:06 -0700 (PDT) Message-ID: <26150195.1185483606663.JavaMail.jira@brutus> Date: Thu, 26 Jul 2007 14:00:06 -0700 (PDT) From: "Ole Ersoy (JIRA)" To: dev@directory.apache.org Subject: [jira] Reopened: (DIRSERVER-1010) Should the order in which hot partitions are connected to matter? In-Reply-To: <30455515.1185415171200.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DIRSERVER-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ole Ersoy reopened DIRSERVER-1010: ---------------------------------- OK - To see the behavior, just create an instance of the testing archetype. In there will be the following test: public class ADSEmbeddedHotPartitionTemplateTest extends ADSEmbeddedHotPartitionTemplate { public void tearDown() throws NamingException, Exception { super.tearDown(); } public void setUp() throws Exception { super.setUp(); } public void testSchemaConnect() throws NamingException { LdapContext ldapContext = null; ldapContext = connect("test"); assertEquals( "ou=test", ldapContext.getNameInNamespace()); } } Change it to look like this: public class ADSEmbeddedHotPartitionTemplateTest extends ADSEmbeddedHotPartitionTemplate { public void tearDown() throws NamingException, Exception { super.tearDown(); } public void setUp() throws Exception { super.setUp(); } public void testSchemaConnect() throws NamingException { LdapContext ldapContext = null; ldapContext = connect("schema"); ldapContext = connect("test"); assertEquals( "ou=test", ldapContext.getNameInNamespace()); } } Now the exception will be thrown. Note that the server-work directory should not exist prior to running the test. > 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 > Reporter: Ole Ersoy > > 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.