Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 22896 invoked from network); 20 Jul 2007 21:12:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Jul 2007 21:12:47 -0000 Received: (qmail 39673 invoked by uid 500); 20 Jul 2007 21:12:48 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 39637 invoked by uid 500); 20 Jul 2007 21:12:48 -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 39625 invoked by uid 99); 20 Jul 2007 21:12:48 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jul 2007 14:12:48 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of ole.ersoy@gmail.com designates 64.233.166.177 as permitted sender) Received: from [64.233.166.177] (HELO py-out-1112.google.com) (64.233.166.177) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Jul 2007 14:12:45 -0700 Received: by py-out-1112.google.com with SMTP id d32so2222780pye for ; Fri, 20 Jul 2007 14:12:25 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=DQhrapvXuhKZKDzMRVl0RnIpHAxdP/pr+mpM5LbKh+yIG7wAr9BwdiGzL13ZM9+U/J+Ly3X52X+Ib3gXrqiGmYXoQj/hrLtMQFPETxpyi2YCTrryfjQL2Ys5rfe1RfdCqeG9g3jU64jhJ9mzNAk371t2VHWnQzLitq6T3SGmtwc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=Q7jyoFMbQSpa+5EY4QT5i0BT4oRu9wMh+5mu8nseKK3ny5jqW2gpRJ92FE9Ztvaf8nxYKfZS0HeXcfsjw9Bbp4SZck1OiH2SdRwH8d27BwIIET5Nn1ZZ0t1mWDK6fCbFNLe47u0w7Gv77sqaOfkD4rWOxnku6z3ArOfdC9i8o8Q= Received: by 10.65.211.16 with SMTP id n16mr1635122qbq.1184965944526; Fri, 20 Jul 2007 14:12:24 -0700 (PDT) Received: from ?192.168.1.6? ( [24.13.164.174]) by mx.google.com with ESMTPS id q17sm995093qbq.2007.07.20.14.12.23 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 20 Jul 2007 14:12:24 -0700 (PDT) Message-ID: <46A124D1.5020105@gmail.com> Date: Fri, 20 Jul 2007 16:10:41 -0500 From: Ole Ersoy User-Agent: Thunderbird 2.0.0.4 (X11/20070615) MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: [JNDI] LdapContext.destroyContext() Bug? References: <469FD16A.6020909@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hey Emmanuel, Sorry - My bad. I looked a little more closely at the stack trace and discovered the exception was being thrown during tearDown(). Before I was just testing data graph reading and writing, thus tearing down all created dataobjects manually, and now I'm testing the change summary processing, so I ended up attempting to delete objects that the change summary had already deleted. Sorry for the noise, - Ole Emmanuel Lecharny wrote: > Hi Ole, > > can you provide a full fonctionning tests exposing the incorrect behavior ? > > Thanks ! > > On 7/19/07, Ole Ersoy wrote: >> Hey Guys, >> >> I'm wondering whether the LdapContext.destroySubcontext() method is >> working properly? I have some code like this: >> =================================================================================== >> >> String destroyedObjectRelativeDN = >> dataObjectToRelativeDNCache.get(destroyedObject); >> LdapContext destroyedContext = >> (LdapContext) containerContext.lookup(destroyedObjectRelativeDN); >> >> System.out.println(destroyedContext.getNameInNamespace()); >> =================================================================================== >> >> >> If I run this I get what I expect, which is: >> =================================================================================== >> >> example-com-users-accounts-Authorization-id=2,cn=authorizationList,example-com-users-accounts-User-id=1,cn=accounts,cn=users,cn=example,cn=com,ou=das >> >> example-com-users-accounts-Authorization-id=3,cn=authorizationList,example-com-users-accounts-User-id=1,cn=accounts,cn=users,cn=example,cn=com,ou=das >> >> example-com-users-accounts-Configuration-id=5,cn=configuration,example-com-users-accounts-User-id=1,cn=accounts,cn=users,cn=example,cn=com,ou=das >> >> =================================================================================== >> >> >> So the container context is able to lookup all the contexts that it >> should be able to lookup. However if I change the code and ask it to >> destroy these contexts like this: >> >> containerContext.destroySubcontext(destroyedObjectRelativeDN); >> >> I get an exception like this: >> ========================================================================================================== >> >> org.apache.directory.shared.ldap.exception.LdapNameNotFoundException: >> Attempt to lookup non-existant entry: >> example-com-users-accounts-authorization-id=2,2.5.4.3=authorizationlist,example-com-users-accounts-user-id=1,2.5.4.3=accounts,2.5.4.3=users,2.5.4.3=example,2.5.4.3=com,2.5.4.11=das >> >> at >> org.apache.directory.server.core.exception.ExceptionService.assertHasEntry(ExceptionService.java:573) >> >> at >> org.apache.directory.server.core.exception.ExceptionService.lookup(ExceptionService.java:292) >> >> at >> org.apache.directory.server.core.interceptor.InterceptorChain.lookup(InterceptorChain.java:848) >> >> at >> >> This seems off, since we know that this entry really does exist.... >> >> Thoughts? >> >> Thanks, >> - Ole >> >> >> >> > >