It started pumping out startup stuff this time, but then ended in the same boat I think:

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)

I can probably try to build the 1.5.1-snap again tonight or this weekend and work from that if need be. What would be the easiest way to move my partitions?

-Matt

Emmanuel Lecharny wrote:
Matthew Schmidt a écrit :

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

Ok.

Could you try to add those lines :
log4j.logger.org.apache.directory.server.core.schema=WARN
log4j.logger.org.apache.directory.server.schema.bootstrap=WARN
log4j.logger.org.apache.directory.shared.ldap.schema=WARN

?

Emmanuel

Reply via email to