Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 32819 invoked from network); 5 Feb 2009 18:12:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Feb 2009 18:12:27 -0000 Received: (qmail 81135 invoked by uid 500); 5 Feb 2009 18:12:23 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 81096 invoked by uid 500); 5 Feb 2009 18:12:23 -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 81082 invoked by uid 99); 5 Feb 2009 18:12:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Feb 2009 10:12:23 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Feb 2009 18:12:21 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id D8A14234C4A9 for ; Thu, 5 Feb 2009 10:11:59 -0800 (PST) Message-ID: <1731838987.1233857519886.JavaMail.jira@brutus> Date: Thu, 5 Feb 2009 10:11:59 -0800 (PST) From: "Emmanuel Lecharny (JIRA)" To: dev@directory.apache.org Subject: [jira] Resolved: (DIRSERVER-1306) Searching an attribute which is a DN ends with a 80 Ldap error (Other) In-Reply-To: <1470747274.1233855959826.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-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Lecharny resolved DIRSERVER-1306. ------------------------------------------ Resolution: Invalid My schema was incorrect : I didn't declared an EQUALITY matchingRule for the DN. Hence the DN was considered as a binary attribute, compared accordingly. > Searching an attribute which is a DN ends with a 80 Ldap error (Other) > ---------------------------------------------------------------------- > > Key: DIRSERVER-1306 > URL: https://issues.apache.org/jira/browse/DIRSERVER-1306 > Project: Directory ApacheDS > Issue Type: Bug > Affects Versions: 1.5.4 > Reporter: Emmanuel Lecharny > Priority: Critical > Fix For: 1.5.5 > > > When searching for an entry containing an attribute which has a DN syntax, the server is using a default comparator leading to a Classcast exception : > javax.naming.NamingException: [LDAP: error code 80 - OTHER: failed for SearchRequest > baseDn : '2.5.4.11=softwares,0.9.2342.19200300.100.1.25=company,0.9.2342.19200300.100.1.25=com' > filter : '(1.2.3.2.30=secu-applicationid=WSER,ou=Applications,dc=company,dc=com:[9223372036854775807])' > scope : single level > typesOnly : false > Size Limit : no limit > Time Limit : no limit > Deref Aliases : deref Always > attributes : 'secu-softwareid' > : java.lang.String cannot be cast to [B]; remaining name 'ou=Softwares' > at com.sun.jndi.ldap.LdapCtx.mapErrorCode(Unknown Source) > at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source) > at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source) > at com.sun.jndi.ldap.LdapCtx.searchAux(Unknown Source) > at com.sun.jndi.ldap.LdapCtx.c_search(Unknown Source) > at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(Unknown Source) > at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(Unknown Source) > at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(Unknown Source) > at com.company.secu.ldap.entity.SoftwareLDAP.findAllSoftware(SoftwareLDAP.java:128) > at com.company.websecu.ldap.SoftwareLdapTest.findAllSoftwareByApplicationIdTest(SoftwareLdapTest.java:250) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.junit.internal.runners.TestMethod.invoke(TestMethod.java:66) > at org.junit.internal.runners.MethodRoadie.runTestMethod(MethodRoadie.java:105) > at org.junit.internal.runners.MethodRoadie$2.run(MethodRoadie.java:86) > at org.junit.internal.runners.MethodRoadie.runBeforesThenTestThenAfters(MethodRoadie.java:94) > at org.junit.internal.runners.MethodRoadie.runTest(MethodRoadie.java:84) > at org.junit.internal.runners.MethodRoadie.run(MethodRoadie.java:49) > at org.apache.directory.server.integ.state.TestServerContext.invokeTest(TestServerContext.java:211) > at org.apache.directory.server.integ.state.StartedNormalState.test(StartedNormalState.java:173) > at org.apache.directory.server.integ.state.TestServerContext.test(TestServerContext.java:187) > at org.apache.directory.server.integ.SiRunner.invokeTestMethod(SiRunner.java:103) > at org.junit.internal.runners.JUnit4ClassRunner.runMethods(JUnit4ClassRunner.java:59) > at org.junit.internal.runners.JUnit4ClassRunner$1.run(JUnit4ClassRunner.java:52) > at org.junit.internal.runners.ClassRoadie.runUnprotected(ClassRoadie.java:34) > at org.junit.internal.runners.ClassRoadie.runProtected(ClassRoadie.java:44) > at org.junit.internal.runners.JUnit4ClassRunner.run(JUnit4ClassRunner.java:50) > at org.apache.directory.server.integ.SiRunner.run(SiRunner.java:77) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:45) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.