Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 35216 invoked from network); 18 Aug 2008 14:16:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Aug 2008 14:16:13 -0000 Received: (qmail 7558 invoked by uid 500); 18 Aug 2008 14:16:12 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 7346 invoked by uid 500); 18 Aug 2008 14:16:11 -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 7335 invoked by uid 99); 18 Aug 2008 14:16:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Aug 2008 07:16:11 -0700 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; Mon, 18 Aug 2008 14:15:15 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 4AB6A234C1B6 for ; Mon, 18 Aug 2008 07:15:44 -0700 (PDT) Message-ID: <282514498.1219068944304.JavaMail.jira@brutus> Date: Mon, 18 Aug 2008 07:15:44 -0700 (PDT) From: "Emmanuel Lecharny (JIRA)" To: dev@directory.apache.org Subject: [jira] Commented: (DIRSERVER-1211) Error code 54 in modify-replace operation In-Reply-To: <1603472058.1217193811693.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-1211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623355#action_12623355 ] Emmanuel Lecharny commented on DIRSERVER-1211: ---------------------------------------------- Looking at the stack trace, and looking at the code at JdbmStrore.replace() : private void replace( Long id, ServerEntry entry, EntryAttribute mods ) throws Exception { if ( entry instanceof ClonedServerEntry ) { throw new Exception( "Cannot store a ClonedServerEntry" ); } String modsOid = oidRegistry.getOid( mods.getId() ); if ( hasUserIndexOn( modsOid ) ) { Index index = getUserIndex( modsOid ); // Drop all existing attribute value index entries and add new ones ( ( JdbmIndex ) index ).drop( id ); <-- here, we get the exception ... I'm just thinking that we are trying to remove a reference from an index, but as we are trying to add a new value to thoe indexed attribute, there is no chance this reference could be found in the index. One more check is necessary here: the modified attribute should already exist in the entry before trying to remove the reference to this entry into the index. Thoughts ? > Error code 54 in modify-replace operation > ----------------------------------------- > > Key: DIRSERVER-1211 > URL: https://issues.apache.org/jira/browse/DIRSERVER-1211 > Project: Directory ApacheDS > Issue Type: Bug > Affects Versions: 1.5.3 > Reporter: Stefan Seelmann > Assignee: Emmanuel Lecharny > > This error occurs with apacheds-1.5.3-fixed.tar.gz and the current trunk-with-dependencies (Revision 680187), both with default server.xml > I use studio to run the following LDIF: > --------------------------------------------- > dn: cn=Kate Bush,ou=system > changetype: add > objectClass: top > objectClass: person > objectClass: organizationalPerson > objectClass: inetOrgPerson > cn: Kate Bush > sn: Bush > dn: cn=Kate Bush,ou=system > changetype: modify > replace: ou > ou: Test > - > --------------------------------------------- > The second LDIF record fails with error 54. The log is here: http://www.pastebin.org/57617. > The error does not occur when I use 'add:ou' instead of 'replace:ou' > The error does not occur when I use another attribute, e.g. 'decription' instead of 'ou' > Emmanuel's idea on IM was that it is because 'ou' is indexed in the default server.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.