Return-Path: Delivered-To: apmail-directory-users-archive@www.apache.org Received: (qmail 95244 invoked from network); 20 Apr 2007 21:10:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Apr 2007 21:10:42 -0000 Received: (qmail 6898 invoked by uid 500); 20 Apr 2007 21:10:49 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 6839 invoked by uid 500); 20 Apr 2007 21:10:49 -0000 Mailing-List: contact users-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@directory.apache.org Delivered-To: mailing list users@directory.apache.org Received: (qmail 6828 invoked by uid 99); 20 Apr 2007 21:10:49 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Apr 2007 14:10:49 -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 matt@dzone.com designates 64.246.49.135 as permitted sender) Received: from [64.246.49.135] (HELO usermagnet.com) (64.246.49.135) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Apr 2007 14:10:42 -0700 Received: from [66.57.94.83] (account matt@javalobby.org HELO [10.64.64.3]) by usermagnet.com (CommuniGate Pro SMTP 5.1.7) with ESMTPA id 11608346 for users@directory.apache.org; Fri, 20 Apr 2007 17:10:21 -0400 Message-ID: <46292C23.3080206@dzone.com> Date: Fri, 20 Apr 2007 17:09:55 -0400 From: Matthew Schmidt User-Agent: Thunderbird 2.0b2 (Windows/20070116) MIME-Version: 1.0 To: users@directory.apache.org Subject: Re: Problem searching and binding from PHP and SugarCRM References: <46290349.7070604@dzone.com> <46290D15.1070000@dzone.com> <46292018.2020907@dzone.com> <46292322.1030104@gmail.com> <46292715.7050600@dzone.com> <46292AC1.50002@gmail.com> In-Reply-To: <46292AC1.50002@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org I tried adding the line and I get the same error. Here's my log4j.properties: log4j.rootCategory=DEBUG, stdout, R log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout.layout=org.apache.log4j.PatternLayout log4j.appender.R=org.apache.log4j.RollingFileAppender log4j.appender.R.File=apacheds-rolling.log log4j.appender.R.MaxFileSize=1024KB # Keep some backup files log4j.appender.R.MaxBackupIndex=5 log4j.appender.R.layout=org.apache.log4j.PatternLayout log4j.appender.R.layout.ConversionPattern=[%d{HH:mm:ss}] %p [%c] - %m%n log4j.appender.stdout.layout.ConversionPattern=[%d{HH:mm:ss}] %p [%c] - %m%n # with these we'll not get innundated when switching to DEBUG log4j.logger.org.apache.directory.shared.ldap.name=WARN log4j.logger.org.springframework=WARN log4j.logger.org.apache.directory.shared.codec=WARN log4j.logger.org.apache.directory.shared.asn1=WARN log4j.logger.org.apache.directory.server.schema.registries.DefaultSyntaxRegistry=WARN -Matt Emmanuel Lecharny wrote: > Matthew Schmidt a �crit : > >> Hi guys. For some reason when I turn on DEBUG mode for log4j the >> system throws an exception in both normal and debug mode: > > This is a bug we have fixed in 1.5.1-SNAPSHOT. > > Just add a line at the end of the log4j.property : > log4j.logger.org.apache.directory.server.schema.registries.DefaultSyntaxRegistry=WARN > > > The error should not happen. > > Sorry about this pb... > >> >> [16:52:55] ERROR [org.apache.directory.daemon.Bootstrapper] - Failed >> on org.apache.directory.server.Service.init(InstallationLayout, >> String[]) >> java.lang.ArrayIndexOutOfBoundsException: 0 >> at >> org.apache.directory.shared.ldap.schema.AbstractSchemaObject.toString(AbstractSchemaObject.java:320) >> >> at java.lang.String.valueOf(String.java:2827) >> at java.lang.StringBuilder.append(StringBuilder.java:115) >> at >> org.apache.directory.server.schema.registries.DefaultSyntaxRegistry.register(DefaultSyntaxRegistry.java:110) >> >> at >> org.apache.directory.server.core.schema.PartitionSchemaLoader.loadSyntaxes(PartitionSchemaLoader.java:654) >> >> at >> org.apache.directory.server.core.schema.PartitionSchemaLoader.load(PartitionSchemaLoader.java:348) >> >> at >> org.apache.directory.server.schema.registries.AbstractSchemaLoader.loadDepsFirst(AbstractSchemaLoader.java:107) >> >> at >> org.apache.directory.server.schema.registries.AbstractSchemaLoader.loadDepsFirst(AbstractSchemaLoader.java:143) >> >> at >> org.apache.directory.server.core.schema.PartitionSchemaLoader.loadWithDependencies(PartitionSchemaLoader.java:320) >> >> at >> org.apache.directory.server.core.schema.PartitionSchemaLoader.loadEnabled(PartitionSchemaLoader.java:222) >> >> at >> org.apache.directory.server.core.DefaultDirectoryService.initialize(DefaultDirectoryService.java:914) >> >> at >> org.apache.directory.server.core.DefaultDirectoryService.startup(DefaultDirectoryService.java:254) >> >> at >> org.apache.directory.server.core.jndi.AbstractContextFactory.getInitialContext(AbstractContextFactory.java:118) >> >> at >> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667) >> at >> javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) >> at javax.naming.InitialContext.init(InitialContext.java:223) >> at javax.naming.InitialContext.(InitialContext.java:197) >> at >> javax.naming.directory.InitialDirContext.(InitialDirContext.java:82) >> >> at org.apache.directory.server.Service.init(Service.java:96) >> at >> org.apache.directory.daemon.Bootstrapper.callInit(Bootstrapper.java:151) >> at >> org.apache.directory.daemon.MainBootstrapper.main(MainBootstrapper.java:79) >> >> >> Any ideas? >> >> -Matt >> >> Emmanuel Lecharny wrote: >> >>> Matthew Schmidt a �crit : >>> >>>> Hi Alex. I'm happy to turn on debugging. At the moment we're >>>> running with the workaround you mentioned earlier this week so I >>>> think as long as the output goes to where I'm routing stdout, then >>>> we should be ok. Would running it in debug mode do this or do I >>>> need to change something in the log4j settings? Thanks for helping >>>> me get this straight. >>> >>> >>> You have to set the first line of log4j to DEBUG, and to restart the >>> server. It should be all good. >>> >>> Emmanuel >>> >> >