You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Ole Ersoy (JIRA)" <ji...@apache.org> on 2007/07/26 03:59:31 UTC
[jira] Created: (DIRSERVER-1010) Should the order in which hot
partitions are connected to matter?
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.
Re: [jira] Created: (DIRSERVER-1010) Should the order in which hot
partitions are connected to matter?
Posted by Ole Ersoy <ol...@gmail.com>.
Actually forget the LdapDASHelperTest...I'll just code a new one real quick that self contained and easier to integrate...
Ole Ersoy (JIRA) wrote:
> 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.
>
>
[jira] Updated: (DIRSERVER-1010) Should the order in which hot
partitions are connected to matter?
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DIRSERVER-1010) Should the order in which hot
partitions are connected to matter?
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1010:
-----------------------------------------
Fix Version/s: (was: 1.5.9)
2.0.0-RC1
Affected to 2.0.0-RC1, we won't release a 1.5.9
> 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: 2.0.0-RC1
>
>
> 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.
[jira] Reopened: (DIRSERVER-1010) Should the order in which hot
partitions are connected to matter?
Posted by "Ole Ersoy (JIRA)" <ji...@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.
[jira] Closed: (DIRSERVER-1010) Should the order in which hot
partitions are connected to matter?
Posted by "Ole Ersoy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ole Ersoy closed DIRSERVER-1010.
--------------------------------
Resolution: Invalid
The order does matter :-)
> 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.
[jira] Updated: (DIRSERVER-1010) Should the order in which hot
partitions are connected to matter?
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1010:
-----------------------------------------
Fix Version/s: (was: 1.5.2)
1.5.3
What would be very usefull is a test case into core-integ.
In the meantime, 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.3
>
>
> 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.
[jira] Commented: (DIRSERVER-1010) Should the order in which hot
partitions are connected to matter?
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515885 ]
Emmanuel Lecharny commented on DIRSERVER-1010:
----------------------------------------------
Ole,
it would be much easier if you provide more informations :
- "just create an instance of the testing archetype" : what does it mean ? Any clear direction ?
- where do we find the ADSEmbeddedHotPartitionTemplate.java class ?
- which jar do we need ?
thanks !
> 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.
[jira] Updated: (DIRSERVER-1010) Should the order in which hot
partitions are connected to matter?
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu updated DIRSERVER-1010:
-------------------------------------
Fix Version/s: (was: 1.5.4)
1.5.9
Have no idea about this after so many changes but this should be an issue we clear out before RC1
> 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.9
>
>
> 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.
[jira] Commented: (DIRSERVER-1010) Should the order in which hot
partitions are connected to matter?
Posted by "Ole Ersoy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515919 ]
Ole Ersoy commented on DIRSERVER-1010:
--------------------------------------
Checkout:
svn co https://svn.apache.org/repos/asf/directory/sandbox/oersoy/apacheds.testing.archetype
cd apacheds.testing.archetype
mvn clean install
Run:
mvn archetype:create -DarchetypeGroupId=org.apache.directory -DarchetypeArtifactId=apacheds.testing.archetype -DarchetypeVersion=1.0.0 -DgroupId="" -DartifactId=archetype.instance.testing
The ADSEmbeddedHotPartitionTemplate will be in the project created by the testing archetype
Standard maven layout
> 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.
Re: [jira] Commented: (DIRSERVER-1010) Should the order in which hot partitions are connected to matter?
Posted by Emmanuel Lecharny <el...@gmail.com>.
Danke !
On 7/26/07, Ole Ersoy <ol...@gmail.com> wrote:
> OK - I'll whip it up, reopen, and attach.
>
> Emmanuel Lecharny wrote:
> > I think the best you can do is to provide a test which expose the problem.
> >
> > On 7/26/07, Ole Ersoy <ol...@gmail.com> wrote:
> >> Should I reopen the bug then? If I connect to the schema first I get
> >> the exception.
> >>
> >> Emmanuel Lecharny wrote:
> >> > The schema partition is used for everything, as all the data stored
> >> > into the server are described by it. So it should be declared first.
> >> >
> >> > On 7/26/07, Ole Ersoy <ol...@gmail.com> wrote:
> >> >> Hey Emmanuel,
> >> >>
> >> >> I went ahead and closed it. It's pretty minor. I have a feeling the
> >> >> order should not matter though. The DAS partition and the schema
> >> >> partition are independent. The layout looks like this:
> >> >>
> >> >> ou=das
> >> >> ou=schema
> >> >>
> >> >> If it were like this or flipped:
> >> >> ou=das, ou=schema
> >> >>
> >> >> then I would understand why the order matters.
> >> >>
> >> >> Thanks,
> >> >> - Ole
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> Emmanuel Lecharny (JIRA) wrote:
> >> >> > [
> >> >>
> >> https://issues.apache.org/jira/browse/DIRSERVER-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515625
> >>
> >> >> ]
> >> >> >
> >> >> > Emmanuel Lecharny commented on DIRSERVER-1010:
> >> >> > ----------------------------------------------
> >> >> >
> >> >> > Actually, as you can see in the stack trace, if you invert the
> >> >> order, there is a search done in the partition table, and if the
> >> >> partition does not exist, you get an error. So, basically, yes, order
> >> >> matters.
> >> >> >
> >> >> >> 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.
> >> >> >
> >> >>
> >> >
> >> >
> >>
> >
> >
>
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: [jira] Commented: (DIRSERVER-1010) Should the order in which
hot partitions are connected to matter?
Posted by Ole Ersoy <ol...@gmail.com>.
OK - I'll whip it up, reopen, and attach.
Emmanuel Lecharny wrote:
> I think the best you can do is to provide a test which expose the problem.
>
> On 7/26/07, Ole Ersoy <ol...@gmail.com> wrote:
>> Should I reopen the bug then? If I connect to the schema first I get
>> the exception.
>>
>> Emmanuel Lecharny wrote:
>> > The schema partition is used for everything, as all the data stored
>> > into the server are described by it. So it should be declared first.
>> >
>> > On 7/26/07, Ole Ersoy <ol...@gmail.com> wrote:
>> >> Hey Emmanuel,
>> >>
>> >> I went ahead and closed it. It's pretty minor. I have a feeling the
>> >> order should not matter though. The DAS partition and the schema
>> >> partition are independent. The layout looks like this:
>> >>
>> >> ou=das
>> >> ou=schema
>> >>
>> >> If it were like this or flipped:
>> >> ou=das, ou=schema
>> >>
>> >> then I would understand why the order matters.
>> >>
>> >> Thanks,
>> >> - Ole
>> >>
>> >>
>> >>
>> >>
>> >> Emmanuel Lecharny (JIRA) wrote:
>> >> > [
>> >>
>> https://issues.apache.org/jira/browse/DIRSERVER-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515625
>>
>> >> ]
>> >> >
>> >> > Emmanuel Lecharny commented on DIRSERVER-1010:
>> >> > ----------------------------------------------
>> >> >
>> >> > Actually, as you can see in the stack trace, if you invert the
>> >> order, there is a search done in the partition table, and if the
>> >> partition does not exist, you get an error. So, basically, yes, order
>> >> matters.
>> >> >
>> >> >> 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.
>> >> >
>> >>
>> >
>> >
>>
>
>
Re: [jira] Commented: (DIRSERVER-1010) Should the order in which hot partitions are connected to matter?
Posted by Emmanuel Lecharny <el...@gmail.com>.
I think the best you can do is to provide a test which expose the problem.
On 7/26/07, Ole Ersoy <ol...@gmail.com> wrote:
> Should I reopen the bug then? If I connect to the schema first I get the exception.
>
> Emmanuel Lecharny wrote:
> > The schema partition is used for everything, as all the data stored
> > into the server are described by it. So it should be declared first.
> >
> > On 7/26/07, Ole Ersoy <ol...@gmail.com> wrote:
> >> Hey Emmanuel,
> >>
> >> I went ahead and closed it. It's pretty minor. I have a feeling the
> >> order should not matter though. The DAS partition and the schema
> >> partition are independent. The layout looks like this:
> >>
> >> ou=das
> >> ou=schema
> >>
> >> If it were like this or flipped:
> >> ou=das, ou=schema
> >>
> >> then I would understand why the order matters.
> >>
> >> Thanks,
> >> - Ole
> >>
> >>
> >>
> >>
> >> Emmanuel Lecharny (JIRA) wrote:
> >> > [
> >> https://issues.apache.org/jira/browse/DIRSERVER-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515625
> >> ]
> >> >
> >> > Emmanuel Lecharny commented on DIRSERVER-1010:
> >> > ----------------------------------------------
> >> >
> >> > Actually, as you can see in the stack trace, if you invert the
> >> order, there is a search done in the partition table, and if the
> >> partition does not exist, you get an error. So, basically, yes, order
> >> matters.
> >> >
> >> >> 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.
> >> >
> >>
> >
> >
>
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: [jira] Commented: (DIRSERVER-1010) Should the order in which
hot partitions are connected to matter?
Posted by Ole Ersoy <ol...@gmail.com>.
Should I reopen the bug then? If I connect to the schema first I get the exception.
Emmanuel Lecharny wrote:
> The schema partition is used for everything, as all the data stored
> into the server are described by it. So it should be declared first.
>
> On 7/26/07, Ole Ersoy <ol...@gmail.com> wrote:
>> Hey Emmanuel,
>>
>> I went ahead and closed it. It's pretty minor. I have a feeling the
>> order should not matter though. The DAS partition and the schema
>> partition are independent. The layout looks like this:
>>
>> ou=das
>> ou=schema
>>
>> If it were like this or flipped:
>> ou=das, ou=schema
>>
>> then I would understand why the order matters.
>>
>> Thanks,
>> - Ole
>>
>>
>>
>>
>> Emmanuel Lecharny (JIRA) wrote:
>> > [
>> https://issues.apache.org/jira/browse/DIRSERVER-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515625
>> ]
>> >
>> > Emmanuel Lecharny commented on DIRSERVER-1010:
>> > ----------------------------------------------
>> >
>> > Actually, as you can see in the stack trace, if you invert the
>> order, there is a search done in the partition table, and if the
>> partition does not exist, you get an error. So, basically, yes, order
>> matters.
>> >
>> >> 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.
>> >
>>
>
>
Re: [jira] Commented: (DIRSERVER-1010) Should the order in which hot partitions are connected to matter?
Posted by Emmanuel Lecharny <el...@gmail.com>.
The schema partition is used for everything, as all the data stored
into the server are described by it. So it should be declared first.
On 7/26/07, Ole Ersoy <ol...@gmail.com> wrote:
> Hey Emmanuel,
>
> I went ahead and closed it. It's pretty minor. I have a feeling the order should not matter though. The DAS partition and the schema partition are independent. The layout looks like this:
>
> ou=das
> ou=schema
>
> If it were like this or flipped:
> ou=das, ou=schema
>
> then I would understand why the order matters.
>
> Thanks,
> - Ole
>
>
>
>
> Emmanuel Lecharny (JIRA) wrote:
> > [ https://issues.apache.org/jira/browse/DIRSERVER-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515625 ]
> >
> > Emmanuel Lecharny commented on DIRSERVER-1010:
> > ----------------------------------------------
> >
> > Actually, as you can see in the stack trace, if you invert the order, there is a search done in the partition table, and if the partition does not exist, you get an error. So, basically, yes, order matters.
> >
> >> 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.
> >
>
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: [jira] Commented: (DIRSERVER-1010) Should the order in which
hot partitions are connected to matter?
Posted by Ole Ersoy <ol...@gmail.com>.
Hey Emmanuel,
I went ahead and closed it. It's pretty minor. I have a feeling the order should not matter though. The DAS partition and the schema partition are independent. The layout looks like this:
ou=das
ou=schema
If it were like this or flipped:
ou=das, ou=schema
then I would understand why the order matters.
Thanks,
- Ole
Emmanuel Lecharny (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/DIRSERVER-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515625 ]
>
> Emmanuel Lecharny commented on DIRSERVER-1010:
> ----------------------------------------------
>
> Actually, as you can see in the stack trace, if you invert the order, there is a search done in the partition table, and if the partition does not exist, you get an error. So, basically, yes, order matters.
>
>> 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.
>
[jira] Commented: (DIRSERVER-1010) Should the order in which hot
partitions are connected to matter?
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515625 ]
Emmanuel Lecharny commented on DIRSERVER-1010:
----------------------------------------------
Actually, as you can see in the stack trace, if you invert the order, there is a search done in the partition table, and if the partition does not exist, you get an error. So, basically, yes, order matters.
> 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.
[jira] Updated: (DIRSERVER-1010) Should the order in which hot
partitions are connected to matter?
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu updated DIRSERVER-1010:
-------------------------------------
Fix Version/s: (was: 1.5.3)
1.5.4
> 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.4
>
>
> 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.
[jira] Closed: (DIRSERVER-1010) Should the order in which hot
partitions are connected to matter?
Posted by "Kiran Ayyagari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kiran Ayyagari closed DIRSERVER-1010.
-------------------------------------
Assignee: Kiran Ayyagari
Resolution: Won't Fix
Don't think this issue is valid after many refactorings and design changes. Closing.
> 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
> Assignee: Kiran Ayyagari
> Fix For: 2.0.0-RC1
>
>
> 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.