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.<init>(InitialContext.java:197)
at
javax.naming.directory.InitialDirContext.<init>(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
