Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 08CCDD692 for ; Fri, 9 Nov 2012 16:00:23 +0000 (UTC) Received: (qmail 99680 invoked by uid 500); 9 Nov 2012 16:00:22 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 98937 invoked by uid 500); 9 Nov 2012 16:00:15 -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 98663 invoked by uid 99); 9 Nov 2012 16:00:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 09 Nov 2012 16:00:12 +0000 Date: Fri, 9 Nov 2012 16:00:11 +0000 (UTC) From: "Emmanuel Lecharny (JIRA)" To: dev@directory.apache.org Message-ID: <1202183193.92138.1352476812354.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (DIRSERVER-1758) Error when setting the bad alis deref mode in replication MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Emmanuel Lecharny created DIRSERVER-1758: -------------------------------------------- Summary: Error when setting the bad alis deref mode in replication Key: DIRSERVER-1758 URL: https://issues.apache.org/jira/browse/DIRSERVER-1758 Project: Directory ApacheDS Issue Type: Bug Affects Versions: 2.0.0-M9 Reporter: Emmanuel Lecharny Fix For: 2.0.0-M9 If we set the value of the ads-replAliasDerefMode parameter to "always", we get this exception : [16:53:30] WARN [org.apache.directory.server.core.DefaultDirectoryService] - You didn't change the admin password of directory service instance 'default'. Please update the admin password as soon as possible to prevent a possible security breach. org.apache.directory.server.config.ConfigurationException: cannot configure the replication consumer with FQCN null at org.apache.directory.server.config.builder.ServiceBuilder.createReplConsumers(ServiceBuilder.java:1072) at org.apache.directory.server.config.builder.ServiceBuilder.createLdapServer(ServiceBuilder.java:992) at org.apache.directory.server.ApacheDsService.startLdap(ApacheDsService.java:372) at org.apache.directory.server.ApacheDsService.start(ApacheDsService.java:183) at org.apache.directory.server.UberjarMain.main(UberjarMain.java:58) Caused by: java.lang.IllegalArgumentException: alias deref mode should only be set to either 'NEVER_DEREF_ALIASES' or 'DEREF_FINDING_BASE_OBJ' at org.apache.directory.server.ldap.replication.SyncreplConfiguration.setAliasDerefMode(SyncreplConfiguration.java:429) at org.apache.directory.server.config.builder.ServiceBuilder.createReplConsumers(ServiceBuilder.java:1042) ... 4 more [16:53:30] ERROR [org.apache.directory.server.UberjarMain] - Failed to start the service. org.apache.directory.server.config.ConfigurationException: cannot configure the replication consumer with FQCN null at org.apache.directory.server.config.builder.ServiceBuilder.createReplConsumers(ServiceBuilder.java:1072) at org.apache.directory.server.config.builder.ServiceBuilder.createLdapServer(ServiceBuilder.java:992) at org.apache.directory.server.ApacheDsService.startLdap(ApacheDsService.java:372) at org.apache.directory.server.ApacheDsService.start(ApacheDsService.java:183) at org.apache.directory.server.UberjarMain.main(UberjarMain.java:58) Caused by: java.lang.IllegalArgumentException: alias deref mode should only be set to either 'NEVER_DEREF_ALIASES' or 'DEREF_FINDING_BASE_OBJ' at org.apache.directory.server.ldap.replication.SyncreplConfiguration.setAliasDerefMode(SyncreplConfiguration.java:429) at org.apache.directory.server.config.builder.ServiceBuilder.createReplConsumers(ServiceBuilder.java:1042) ... 4 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira