ADS called from JUnit fails to start with fine-grained logging level
--------------------------------------------------------------------
Key: DIRSERVER-983
URL: https://issues.apache.org/jira/browse/DIRSERVER-983
Project: Directory ApacheDS
Issue Type: Bug
Affects Versions: 1.5.0
Environment: Win XP SP2, J2RE 1.5.0, eclipse 3.2.0, ADS 1.5.0,
slf4j-jdk14-1.2.jar (slf4j-jdk14-1.3.jar, or slf4j-jdk14-1.4.jar)
Reporter: hirot
A JUnit test running on eclipse cannot start embedded Apache Directory Server
because of NamingException caused by ArrayOutOfBoudnsException, when logging
level is FINE, FINER, FINEST, or ALL for JDK logger. However, it can start ADS
well with INFO, WARNING, or SEVERE as JDK logging level.
The environment is :
- Win XP SP2
- J2RE 1.5.0
- eclipse 3.2.0
- ADS 1.5.0
- slf4j-jdk14-1.2.jar (slf4j-jdk14-1.3.jar, or slf4j-jdk14-1.4.jar)
The logging level setting in logging.properties of J2RE is :
.level = ALL
or
org.apache.directory.level = ALL
The stack tracs is :
java.lang.ArrayIndexOutOfBoundsException
at
org.apache.directory.shared.ldap.schema.AbstractSchemaObject.toString(AbstractSchemaObject.java:320)
at java.lang.String.valueOf(String.java:1499)
at java.lang.StringBuilder.append(StringBuilder.java:194)
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:679)
at
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:259)
at javax.naming.InitialContext.init(InitialContext.java:235)
at
javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:146)
Thank you.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
