directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ole Ersoy (JIRA)" <j...@apache.org>
Subject [jira] Created: (DIRSERVER-944) Hot Partition Testing
Date Fri, 25 May 2007 18:41:16 GMT
Hot Partition Testing
---------------------

                 Key: DIRSERVER-944
                 URL: https://issues.apache.org/jira/browse/DIRSERVER-944
             Project: Directory ApacheDS
          Issue Type: Bug
         Environment: FC6
            Reporter: Ole Ersoy


I'm starting this to track observations regarding
the hot partition context I'm using.

This is part of the DAS specific testing, so I'll link 
the observations to specific tests once I check
in the DAS code again.

=====================================================================
The below test passes.  However, if I comment out
the line 
dasPartitionContext.destroySubcontext( testContextDN );
the entry remains INvisible to LS Browser on a browser refresh.
=====================================================================
    /*
     * Create the ou=das partition and the cn=newContext
     * under it.  See whether cn=newContext shows up
     * programmatically and in LS visually.
     */
    public void testCreateDASSubContext() throws NamingException
    {
        String testContextDN      = "cn=newContext";

        dasPartitionContext.createSubcontext( testContextDN );
        
        assertNotNull( dasPartitionContext.lookup(testContextDN) );

        dasPartitionContext.destroySubcontext( testContextDN );
    }
================================================================================




=====================================================================
If I first do a "hot partition connection" to ou=system and then try create another
hot partition ou=das I get the following:

org.apache.directory.shared.ldap.exception.LdapNameNotFoundException: ou=das
	at org.apache.directory.server.core.partition.DefaultPartitionNexus.getBackend(DefaultPartitionNexus.java:987)

Note however that if I create the ou=das partition first, before trying to connect to
existing system partition, and then connect to the ou=das partition again after that,
it works.  So in other words, connecting to ou=system seems to disable the ability to 
create other hot partitions.  
=====================================================================
    public void testCreateDualHotPartitions() 
    throws NamingException
    {
        connectionManager.setDasPartitionName( "system" );
        dasPartitionContext = connectionManager.createDASPartition();
        
        boolean hasFailed = false;
        
        try 
        {
            connectionManager.setDasPartitionName( "das" );
            dasPartitionContext = connectionManager.createDASPartition();
        }
        catch(Exception e)
        {
            hasFailed = true;
        }
        assertTrue(hasFailed);
    }
=====================================================================

So these are observations from using the ADS JNDI Context Factory to create the hot partitions.

Next I need to test creating hot partition entries, and then trying to see them 
with regular with a sun JNDI Context factory.

I think there was a bug here as well.  This will probably overlap with some previous posts,
but It helps me track better as solidify the testing.



-- 
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