You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Ole Ersoy (JIRA)" <ji...@apache.org> on 2007/06/15 07:01:34 UTC
[jira] Created: (DIRSERVER-970) Hot Partition Fails With
ArrayIndexOutOfBoundsException
Hot Partition Fails With ArrayIndexOutOfBoundsException
-------------------------------------------------------
Key: DIRSERVER-970
URL: https://issues.apache.org/jira/browse/DIRSERVER-970
Project: Directory ApacheDS
Issue Type: Bug
Reporter: Ole Ersoy
After building the ApacheDS trunk on my machine, I started getting strange results when running tests. So I cleaned out the Maven repository completely, rebuilt ADS, and started from scratch. Now when I try to run the attached test (Needs a running server), I get this:
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:103)
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.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
at org.apache.tuscany.das.ldap.learning.test.IndependentHotPartitionTest.createDASPartition(IndependentHotPartitionTest.java:80)
at org.apache.tuscany.das.ldap.learning.test.IndependentHotPartitionTest.testCreateDASPartition(IndependentHotPartitionTest.java:30)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-970) Hot Partition Fails With
ArrayIndexOutOfBoundsException
Posted by "Ole Ersoy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ole Ersoy updated DIRSERVER-970:
--------------------------------
Attachment: IndependentHotPartitionTest.java
> Hot Partition Fails With ArrayIndexOutOfBoundsException
> -------------------------------------------------------
>
> Key: DIRSERVER-970
> URL: https://issues.apache.org/jira/browse/DIRSERVER-970
> Project: Directory ApacheDS
> Issue Type: Bug
> Reporter: Ole Ersoy
> Attachments: IndependentHotPartitionTest.java
>
>
> After building the ApacheDS trunk on my machine, I started getting strange results when running tests. So I cleaned out the Maven repository completely, rebuilt ADS, and started from scratch. Now when I try to run the attached test (Needs a running server), I get this:
> 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:103)
> 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.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
> at org.apache.tuscany.das.ldap.learning.test.IndependentHotPartitionTest.createDASPartition(IndependentHotPartitionTest.java:80)
> at org.apache.tuscany.das.ldap.learning.test.IndependentHotPartitionTest.testCreateDASPartition(IndependentHotPartitionTest.java:30)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-970) Hot Partition Fails With
ArrayIndexOutOfBoundsException
Posted by "Ole Ersoy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505041 ]
Ole Ersoy commented on DIRSERVER-970:
-------------------------------------
Just noticed that the attached test uses constants from an external interface. These are the values used:
String SIMPLE_SECURITY_AUTHENTICATION_VALUE =
"simple";
String DEFAULT_SECURITY_PRINCIPAL_VALUE =
"uid=admin,ou=system";
String DEFAULT_SECURITY_CREDENTIALS_VALUE =
"secret";
> Hot Partition Fails With ArrayIndexOutOfBoundsException
> -------------------------------------------------------
>
> Key: DIRSERVER-970
> URL: https://issues.apache.org/jira/browse/DIRSERVER-970
> Project: Directory ApacheDS
> Issue Type: Bug
> Reporter: Ole Ersoy
> Attachments: IndependentHotPartitionTest.java
>
>
> After building the ApacheDS trunk on my machine, I started getting strange results when running tests. So I cleaned out the Maven repository completely, rebuilt ADS, and started from scratch. Now when I try to run the attached test (Needs a running server), I get this:
> 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:103)
> 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.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
> at org.apache.tuscany.das.ldap.learning.test.IndependentHotPartitionTest.createDASPartition(IndependentHotPartitionTest.java:80)
> at org.apache.tuscany.das.ldap.learning.test.IndependentHotPartitionTest.testCreateDASPartition(IndependentHotPartitionTest.java:30)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DIRSERVER-970) Hot Partition Fails With
ArrayIndexOutOfBoundsException
Posted by "Ole Ersoy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ole Ersoy closed DIRSERVER-970.
-------------------------------
Resolution: Fixed
Built with 1.5.0 branch by "Accident". Sorry for the noise.
> Hot Partition Fails With ArrayIndexOutOfBoundsException
> -------------------------------------------------------
>
> Key: DIRSERVER-970
> URL: https://issues.apache.org/jira/browse/DIRSERVER-970
> Project: Directory ApacheDS
> Issue Type: Bug
> Reporter: Ole Ersoy
> Attachments: IndependentHotPartitionTest.java
>
>
> After building the ApacheDS trunk on my machine, I started getting strange results when running tests. So I cleaned out the Maven repository completely, rebuilt ADS, and started from scratch. Now when I try to run the attached test (Needs a running server), I get this:
> 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:103)
> 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.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
> at org.apache.tuscany.das.ldap.learning.test.IndependentHotPartitionTest.createDASPartition(IndependentHotPartitionTest.java:80)
> at org.apache.tuscany.das.ldap.learning.test.IndependentHotPartitionTest.testCreateDASPartition(IndependentHotPartitionTest.java:30)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DIRSERVER-970) Hot Partition Fails With
ArrayIndexOutOfBoundsException
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny resolved DIRSERVER-970.
-----------------------------------------
Resolution: Duplicate
Was fixed in DIRESERVER-902
Switch to a more recent build of the shared-ldap library
> Hot Partition Fails With ArrayIndexOutOfBoundsException
> -------------------------------------------------------
>
> Key: DIRSERVER-970
> URL: https://issues.apache.org/jira/browse/DIRSERVER-970
> Project: Directory ApacheDS
> Issue Type: Bug
> Reporter: Ole Ersoy
> Attachments: IndependentHotPartitionTest.java
>
>
> After building the ApacheDS trunk on my machine, I started getting strange results when running tests. So I cleaned out the Maven repository completely, rebuilt ADS, and started from scratch. Now when I try to run the attached test (Needs a running server), I get this:
> 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:103)
> 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.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
> at org.apache.tuscany.das.ldap.learning.test.IndependentHotPartitionTest.createDASPartition(IndependentHotPartitionTest.java:80)
> at org.apache.tuscany.das.ldap.learning.test.IndependentHotPartitionTest.testCreateDASPartition(IndependentHotPartitionTest.java:30)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (DIRSERVER-970) Hot Partition Fails With
ArrayIndexOutOfBoundsException
Posted by "Ole Ersoy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ole Ersoy reopened DIRSERVER-970:
---------------------------------
I'm reopening this. It's the same exception, but different cause. I tried copying some of the classes from the testing archetype to a different project. When I ran them, I get the same exception. Finally I remembered that the classes need the log4j.properties file, otherwise the embedding will not work.
To see this in action, check out the testing archetype in my sandbox. Run ADSEmbeddedHotPartitionTest. Then remove the log4j configuration file from the test/resources directory.
Here's the link to the testing archetype
svn co https://svn.apache.org/repos/asf/directory/sandbox/oersoy/apacheds.testing.archetype
> Hot Partition Fails With ArrayIndexOutOfBoundsException
> -------------------------------------------------------
>
> Key: DIRSERVER-970
> URL: https://issues.apache.org/jira/browse/DIRSERVER-970
> Project: Directory ApacheDS
> Issue Type: Bug
> Reporter: Ole Ersoy
> Attachments: IndependentHotPartitionTest.java
>
>
> After building the ApacheDS trunk on my machine, I started getting strange results when running tests. So I cleaned out the Maven repository completely, rebuilt ADS, and started from scratch. Now when I try to run the attached test (Needs a running server), I get this:
> 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:103)
> 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.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
> at org.apache.tuscany.das.ldap.learning.test.IndependentHotPartitionTest.createDASPartition(IndependentHotPartitionTest.java:80)
> at org.apache.tuscany.das.ldap.learning.test.IndependentHotPartitionTest.testCreateDASPartition(IndependentHotPartitionTest.java:30)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRSERVER-970) Hot Partition Fails With
ArrayIndexOutOfBoundsException
Posted by "Ole Ersoy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505386 ]
Ole Ersoy commented on DIRSERVER-970:
-------------------------------------
Here's the verification process:
svn co https://svn.apache.org/repos/asf/directory/sandbox/oersoy/apacheds.testing.archetype
cd apacheds.testing.archetype
mvn install
cd ..
Run:
mvn archetype:create -DarchetypeGroupId=org.apache.directory -DarchetypeArtifactId=apacheds.testing.archetype -DarchetypeVersion=1.0.0 -DgroupId="" -DartifactId=archetype.instance.testing
cd archetype.instance.testing
mvn eclipse:eclipse
Import into eclipse
Run the ADSEmbeddedHotPartitionTemplateTest
Now go to: src/test/resources
Rename the logging file. Run the test again.
> Hot Partition Fails With ArrayIndexOutOfBoundsException
> -------------------------------------------------------
>
> Key: DIRSERVER-970
> URL: https://issues.apache.org/jira/browse/DIRSERVER-970
> Project: Directory ApacheDS
> Issue Type: Bug
> Reporter: Ole Ersoy
> Attachments: IndependentHotPartitionTest.java
>
>
> After building the ApacheDS trunk on my machine, I started getting strange results when running tests. So I cleaned out the Maven repository completely, rebuilt ADS, and started from scratch. Now when I try to run the attached test (Needs a running server), I get this:
> 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:103)
> 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.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
> at org.apache.tuscany.das.ldap.learning.test.IndependentHotPartitionTest.createDASPartition(IndependentHotPartitionTest.java:80)
> at org.apache.tuscany.das.ldap.learning.test.IndependentHotPartitionTest.testCreateDASPartition(IndependentHotPartitionTest.java:30)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (DIRSERVER-970) Hot Partition Fails With ArrayIndexOutOfBoundsException
Posted by Ole Ersoy <ol...@gmail.com>.
Yeeeees - I'll close it. Thanks Guys,
- Ole
Emmanuel Lecharny wrote:
> Thanks Chris ! This was your fix ;)
>
> Ole, can you close the JIRA now ?
>
> Thanks !
>
> On 6/16/07, Chris Custine <ch...@gmail.com> wrote:
>> Sorry about that... I started this email and walked away so I didn't see
>> your response. Glad you got that figured out!
>>
>> Chris
>>
>>
>> On 6/15/07, Chris Custine <ch...@gmail.com> wrote:
>> > Hi Ole,
>> > Emmanuel is absolutely right, there is no way the current SVN code is
>> causing a AIOOBE:"
>> >
>> >
>> > > return "<" + oid + ", " + ( ( names == null ) || ( names.length ==
>> 0 ) ?
>> "null" : names[0] ) + ">";
>> >
>> >
>> > AIOOBE just can't happen here anymore. I agree with him also, that you
>> MUST have a pom.xml problem that is causing it to pick up 1.5.0 or a
>> build
>> of 1.5.1-SNAPSHOT prior to the fix being applied.
>> >
>> > Good luck,
>> > Chris
>> >
>> >
>>
>>
>
>
Re: [jira] Commented: (DIRSERVER-970) Hot Partition Fails With ArrayIndexOutOfBoundsException
Posted by Emmanuel Lecharny <el...@gmail.com>.
Thanks Chris ! This was your fix ;)
Ole, can you close the JIRA now ?
Thanks !
On 6/16/07, Chris Custine <ch...@gmail.com> wrote:
> Sorry about that... I started this email and walked away so I didn't see
> your response. Glad you got that figured out!
>
> Chris
>
>
> On 6/15/07, Chris Custine <ch...@gmail.com> wrote:
> > Hi Ole,
> > Emmanuel is absolutely right, there is no way the current SVN code is
> causing a AIOOBE:"
> >
> >
> > > return "<" + oid + ", " + ( ( names == null ) || ( names.length == 0 ) ?
> "null" : names[0] ) + ">";
> >
> >
> > AIOOBE just can't happen here anymore. I agree with him also, that you
> MUST have a pom.xml problem that is causing it to pick up 1.5.0 or a build
> of 1.5.1-SNAPSHOT prior to the fix being applied.
> >
> > Good luck,
> > Chris
> >
> >
>
>
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: [jira] Commented: (DIRSERVER-970) Hot Partition Fails With ArrayIndexOutOfBoundsException
Posted by Ole Ersoy <ol...@gmail.com>.
Hey Chris,
Yeah - We (Emmanuel) finally nailed it. I really thought I was building the trunk, when I was building something else, and since it took care of the first issue, I really thought it was correct. So I was checking my versions against that "Trunk". Turns out there's "Another" trunk :-) Thanks for chiming in though.
Cheers,
- Ole
Chris Custine wrote:
> Sorry about that... I started this email and walked away so I didn't
> see your response. Glad you got that figured out!
>
> Chris
>
> On 6/15/07, *Chris Custine * <chris.custine@gmail.com
> <ma...@gmail.com>> wrote:
>
> Hi Ole,
> Emmanuel is absolutely right, there is no way the current SVN code
> is causing a AIOOBE:
>
> return "<" + oid + ", " + ( ( names == null ) || ( names.length
> == 0 ) ? "null" : names[0] ) + ">";
>
>
> AIOOBE just can't happen here anymore. I agree with him also, that
> you MUST have a pom.xml problem that is causing it to pick up 1.5.0
> or a build of 1.5.1-SNAPSHOT prior to the fix being applied.
>
> Good luck,
> Chris
>
>
>
Re: [jira] Commented: (DIRSERVER-970) Hot Partition Fails With ArrayIndexOutOfBoundsException
Posted by Chris Custine <ch...@gmail.com>.
Sorry about that... I started this email and walked away so I didn't see
your response. Glad you got that figured out!
Chris
On 6/15/07, Chris Custine <ch...@gmail.com> wrote:
>
> Hi Ole,
> Emmanuel is absolutely right, there is no way the current SVN code is
> causing a AIOOBE:
>
> return "<" + oid + ", " + ( ( names == null ) || ( names.length == 0 ) ?
> > "null" : names[0] ) + ">";
>
>
> AIOOBE just can't happen here anymore. I agree with him also, that you
> MUST have a pom.xml problem that is causing it to pick up 1.5.0 or a build
> of 1.5.1-SNAPSHOT prior to the fix being applied.
>
> Good luck,
> Chris
>
>
>
Re: [jira] Commented: (DIRSERVER-970) Hot Partition Fails With ArrayIndexOutOfBoundsException
Posted by Chris Custine <ch...@gmail.com>.
Hi Ole,
Emmanuel is absolutely right, there is no way the current SVN code is
causing a AIOOBE:
return "<" + oid + ", " + ( ( names == null ) || ( names.length == 0 ) ?
> "null" : names[0] ) + ">";
AIOOBE just can't happen here anymore. I agree with him also, that you MUST
have a pom.xml problem that is causing it to pick up 1.5.0 or a build of
1.5.1-SNAPSHOT prior to the fix being applied.
Good luck,
Chris
Re: [jira] Commented: (DIRSERVER-970) Hot Partition Fails With ArrayIndexOutOfBoundsException
Posted by Ole Ersoy <ol...@gmail.com>.
Doh! OK - I should have checked that one more time. I assumed that since I had a problem with the 1.5.0 version before, and then when I checked out the trunk, rebuilt my repository, and ran the test again, and it ran fine, that the thing was OK. It turns out I had a 1.5.0 checkout in my workspace, and that's the one I built, thinking that it was the trunk. Then I looked again, and saw "Trunk with dependencies". Double Doh! So that fixed my initial problem but left this one.
I like the Swallow in a room analogy :-).
OK - I owe a night on the house.
Cheers,
- Ole
Emmanuel Lecharny wrote:
> I did spent the two minutes to go through the steps you gave. Here is
> what I get
> 1) I have lost 2 minutes, which is not really a pb.
> 2) Obviously, you are totally lost in your problem, trying to find a
> problem somewhere where there are not, simply because you are like a
> swallow in a room, bumping your head in all the walls trying
> desesperatly to find an exit
> 3) Simply take a break. When you can't find out the solution, but have
> a workaround, step back, breeze, have a smoke/drink/sleep/pot, and
> come back with a fresh brain
> 4) There is no problem. You simply are using an _old_ version of the
> jars, not the trunk. Your pom.xml is FU. I already told you that, but
> you were stuck in your idea that something should be wrong with the
> code. (bad attitude ...)
> Here is what I get when I run mvn eclipse:eclipse on your project :
> [INFO] Wrote Eclipse project for "archetype.instance.testing" to
> /home/elecharny/apacheds/archetype.instance.testing.
> [INFO]
> Sources for some artifacts are not available.
> Please run the same goal with the -DdownloadSources=true
> parameter in order to check remote repositories for sources.
> List of artifacts without a source archive:
> o xerces:xercesImpl:2.0.2
> o junit:junit:3.8.1
> o antlr:antlr:2.7.6
> o org.apache.directory.server:apacheds-jdbm-store:1.5.0
> o org.apache.directory.shared:shared-ldap-constants:0.9.6
> o jdbm:jdbm:1.0
> o org.slf4j:nlog4j:1.2.25
> o org.apache.directory.server:apacheds-schema-extras:1.5.0
> o commons-lang:commons-lang:2.1
> o org.apache.directory.server:apacheds-schema-bootstrap:1.5.0
> o org.apache.directory.server:apacheds-schema-registries:1.5.0
> o commons-collections:commons-collections:3.0
> o org.apache.directory.shared:shared-ldap:0.9.6
> o org.apache.directory.server:apacheds-core-shared:1.5.0
> o checkstyle:checkstyle:2.2
> o org.apache.directory.server:apacheds-btree-base:1.5.0
> o org.apache.directory.server:apacheds-bootstrap-partition:1.5.0
> o org.apache.directory.server:apacheds-bootstrap-extract:1.5.0
> o org.apache.directory.server:apacheds-constants:1.5.0
> o org.apache.directory.server:apacheds-utils:1.5.0
> o org.apache.directory.server:apacheds-core:1.5.0
> o org.apache.directory.shared:shared-asn1:0.9.6
>
> Obviously, 1.5.0 != 1.5.1-SNAPSHOT and 0.9.6 != 0.9.7-SNAPSHOT
>
> try that in your pom.xml, it should be better :
>
> <dependency>
> <groupId>org.apache.directory.server</groupId>
> <artifactId>apacheds-core</artifactId>
> <version>1.5.1-SNAPSHOT</version>
> </dependency>
>
> Ok, no harm. I just wanted you to realize that you _must_ analyze the
> reasons, not the symptoms. Symptoms does not generate the problem.
> They just exhibit it.
>
> Emmanuel
>
>
>
> On 6/16/07, Ole Ersoy <ol...@gmail.com> wrote:
>> Emmanuel,
>>
>> Here's the thing. I just did a fresh checkout from the trunk. If the
>> logging file is there, the exception is non existent. That means the
>> patch works right? If the logging file is removed or renamed, then
>> the exception happens. I think the only way to verify this is to go
>> through the steps I gave. Could you please just do the steps I gave
>> you? It will only take two two minutes. I promise.
>>
>> I would do the patchy thingy, but that's a learning curve for me. It
>> will take me at least 20 minutes to figure out patchy stuff. Yes it's
>> one of those things I need to learn, but the process I gave you only
>> takes two minutes. I win :-) I'll tell you what. If you run through
>> the steps, and the exception does not occur, I owe you a night of
>> beers in Chicago or Paris, or some convention city, whichever
>> comes first :-)
>>
>> Cheers,
>> - Ole
>>
>> Emmanuel Lecharny wrote:
>> > Ole Ersoy a écrit :
>> >
>> >>
>> >>
>> >> Emmanuel Lecharny wrote:
>> >>
>> >>> Ole Ersoy a écrit :
>> >>>
>> >>>> Emmanuel,
>> >>>>
>> >>>>
>> >>>> Suppose I was using an old jar. Why does my test pass then?
>> >>>
>> >>>
>> >>> I told you three times that the bug happens ONLY if you run the test
>> >>> with a log4j in DEBUG mode, otherwise the toString() method is
>> >>> _never_ called. This is why your test pass when you don't use the
>> >>> logging file.
>> >>
>> >>
>> >> I think this is what you are missing.
>> >>
>> ========================================================================
>> >> This is why your test pass when you don't use the logging file.
>> >>
>> ========================================================================
>> >>
>> >> I am using the logging file. It's only if the logging file is renamed
>> >> or removed that the exception happens.
>> >
>> > Oh, ok. I inverted the context. Nevertheless, this toString() method is
>> > only called when in DEBUG mode. So this is not something you are likely
>> > to have, unless you are in DEBUG mode.
>> >
>> >> I gave the verification process. We've spent way more time discussing
>> >> this than it would have taken you to just run through the verification
>> >> steps. If you tell me that renaming the logging file should cause
>> >> this exception, then I'll close the issue.
>> >
>> > I'm not telling that shooting the messenger (here, the logging file)
>> > will help at all. I just say that - and if you look carefully at the
>> > code I posted - this is definitively *not* a code in the trunk, as it
>> > has been fixed.
>> >
>> > Look at the line 320, and simply tell me if this can throw the
>> exception
>> > or not. If the response is :"yes, this is strange, it should not but I
>> > get the excpetion", then you have *another* problem elsewhere.
>> That's it.
>> >
>> > Do me a favor : patch the code of this method, add a try { ... }
>> catch (
>> > ArrayOutOfBoundException e) { e.printStackTrace(); } in it, and if the
>> > stacktrace is produced, I own you a beer, ok ?
>> >
>> > Thanks.
>> > Emmanuel.
>> >
>> > PS : Chris fixed the bug 3 months ago. I applied the patch. Twice.
>> >
>> >
>> >
>>
>
>
Re: [jira] Commented: (DIRSERVER-970) Hot Partition Fails With ArrayIndexOutOfBoundsException
Posted by Emmanuel Lecharny <el...@gmail.com>.
I did spent the two minutes to go through the steps you gave. Here is what I get
1) I have lost 2 minutes, which is not really a pb.
2) Obviously, you are totally lost in your problem, trying to find a
problem somewhere where there are not, simply because you are like a
swallow in a room, bumping your head in all the walls trying
desesperatly to find an exit
3) Simply take a break. When you can't find out the solution, but have
a workaround, step back, breeze, have a smoke/drink/sleep/pot, and
come back with a fresh brain
4) There is no problem. You simply are using an _old_ version of the
jars, not the trunk. Your pom.xml is FU. I already told you that, but
you were stuck in your idea that something should be wrong with the
code. (bad attitude ...)
Here is what I get when I run mvn eclipse:eclipse on your project :
[INFO] Wrote Eclipse project for "archetype.instance.testing" to
/home/elecharny/apacheds/archetype.instance.testing.
[INFO]
Sources for some artifacts are not available.
Please run the same goal with the -DdownloadSources=true
parameter in order to check remote repositories for sources.
List of artifacts without a source archive:
o xerces:xercesImpl:2.0.2
o junit:junit:3.8.1
o antlr:antlr:2.7.6
o org.apache.directory.server:apacheds-jdbm-store:1.5.0
o org.apache.directory.shared:shared-ldap-constants:0.9.6
o jdbm:jdbm:1.0
o org.slf4j:nlog4j:1.2.25
o org.apache.directory.server:apacheds-schema-extras:1.5.0
o commons-lang:commons-lang:2.1
o org.apache.directory.server:apacheds-schema-bootstrap:1.5.0
o org.apache.directory.server:apacheds-schema-registries:1.5.0
o commons-collections:commons-collections:3.0
o org.apache.directory.shared:shared-ldap:0.9.6
o org.apache.directory.server:apacheds-core-shared:1.5.0
o checkstyle:checkstyle:2.2
o org.apache.directory.server:apacheds-btree-base:1.5.0
o org.apache.directory.server:apacheds-bootstrap-partition:1.5.0
o org.apache.directory.server:apacheds-bootstrap-extract:1.5.0
o org.apache.directory.server:apacheds-constants:1.5.0
o org.apache.directory.server:apacheds-utils:1.5.0
o org.apache.directory.server:apacheds-core:1.5.0
o org.apache.directory.shared:shared-asn1:0.9.6
Obviously, 1.5.0 != 1.5.1-SNAPSHOT and 0.9.6 != 0.9.7-SNAPSHOT
try that in your pom.xml, it should be better :
<dependency>
<groupId>org.apache.directory.server</groupId>
<artifactId>apacheds-core</artifactId>
<version>1.5.1-SNAPSHOT</version>
</dependency>
Ok, no harm. I just wanted you to realize that you _must_ analyze the
reasons, not the symptoms. Symptoms does not generate the problem.
They just exhibit it.
Emmanuel
On 6/16/07, Ole Ersoy <ol...@gmail.com> wrote:
> Emmanuel,
>
> Here's the thing. I just did a fresh checkout from the trunk. If the logging file is there, the exception is non existent. That means the patch works right? If the logging file is removed or renamed, then the exception happens. I think the only way to verify this is to go through the steps I gave. Could you please just do the steps I gave you? It will only take two two minutes. I promise.
>
> I would do the patchy thingy, but that's a learning curve for me. It will take me at least 20 minutes to figure out patchy stuff. Yes it's one of those things I need to learn, but the process I gave you only takes two minutes. I win :-) I'll tell you what. If you run through the steps, and the exception does not occur, I owe you a night of beers in Chicago or Paris, or some convention city, whichever comes first :-)
>
> Cheers,
> - Ole
>
> Emmanuel Lecharny wrote:
> > Ole Ersoy a écrit :
> >
> >>
> >>
> >> Emmanuel Lecharny wrote:
> >>
> >>> Ole Ersoy a écrit :
> >>>
> >>>> Emmanuel,
> >>>>
> >>>>
> >>>> Suppose I was using an old jar. Why does my test pass then?
> >>>
> >>>
> >>> I told you three times that the bug happens ONLY if you run the test
> >>> with a log4j in DEBUG mode, otherwise the toString() method is
> >>> _never_ called. This is why your test pass when you don't use the
> >>> logging file.
> >>
> >>
> >> I think this is what you are missing.
> >> ========================================================================
> >> This is why your test pass when you don't use the logging file.
> >> ========================================================================
> >>
> >> I am using the logging file. It's only if the logging file is renamed
> >> or removed that the exception happens.
> >
> > Oh, ok. I inverted the context. Nevertheless, this toString() method is
> > only called when in DEBUG mode. So this is not something you are likely
> > to have, unless you are in DEBUG mode.
> >
> >> I gave the verification process. We've spent way more time discussing
> >> this than it would have taken you to just run through the verification
> >> steps. If you tell me that renaming the logging file should cause
> >> this exception, then I'll close the issue.
> >
> > I'm not telling that shooting the messenger (here, the logging file)
> > will help at all. I just say that - and if you look carefully at the
> > code I posted - this is definitively *not* a code in the trunk, as it
> > has been fixed.
> >
> > Look at the line 320, and simply tell me if this can throw the exception
> > or not. If the response is :"yes, this is strange, it should not but I
> > get the excpetion", then you have *another* problem elsewhere. That's it.
> >
> > Do me a favor : patch the code of this method, add a try { ... } catch (
> > ArrayOutOfBoundException e) { e.printStackTrace(); } in it, and if the
> > stacktrace is produced, I own you a beer, ok ?
> >
> > Thanks.
> > Emmanuel.
> >
> > PS : Chris fixed the bug 3 months ago. I applied the patch. Twice.
> >
> >
> >
>
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: [jira] Commented: (DIRSERVER-970) Hot Partition Fails With ArrayIndexOutOfBoundsException
Posted by Ole Ersoy <ol...@gmail.com>.
Emmanuel,
Here's the thing. I just did a fresh checkout from the trunk. If the logging file is there, the exception is non existent. That means the patch works right? If the logging file is removed or renamed, then the exception happens. I think the only way to verify this is to go through the steps I gave. Could you please just do the steps I gave you? It will only take two two minutes. I promise.
I would do the patchy thingy, but that's a learning curve for me. It will take me at least 20 minutes to figure out patchy stuff. Yes it's one of those things I need to learn, but the process I gave you only takes two minutes. I win :-) I'll tell you what. If you run through the steps, and the exception does not occur, I owe you a night of beers in Chicago or Paris, or some convention city, whichever comes first :-)
Cheers,
- Ole
Emmanuel Lecharny wrote:
> Ole Ersoy a écrit :
>
>>
>>
>> Emmanuel Lecharny wrote:
>>
>>> Ole Ersoy a écrit :
>>>
>>>> Emmanuel,
>>>>
>>>>
>>>> Suppose I was using an old jar. Why does my test pass then?
>>>
>>>
>>> I told you three times that the bug happens ONLY if you run the test
>>> with a log4j in DEBUG mode, otherwise the toString() method is
>>> _never_ called. This is why your test pass when you don't use the
>>> logging file.
>>
>>
>> I think this is what you are missing.
>> ========================================================================
>> This is why your test pass when you don't use the logging file.
>> ========================================================================
>>
>> I am using the logging file. It's only if the logging file is renamed
>> or removed that the exception happens.
>
> Oh, ok. I inverted the context. Nevertheless, this toString() method is
> only called when in DEBUG mode. So this is not something you are likely
> to have, unless you are in DEBUG mode.
>
>> I gave the verification process. We've spent way more time discussing
>> this than it would have taken you to just run through the verification
>> steps. If you tell me that renaming the logging file should cause
>> this exception, then I'll close the issue.
>
> I'm not telling that shooting the messenger (here, the logging file)
> will help at all. I just say that - and if you look carefully at the
> code I posted - this is definitively *not* a code in the trunk, as it
> has been fixed.
>
> Look at the line 320, and simply tell me if this can throw the exception
> or not. If the response is :"yes, this is strange, it should not but I
> get the excpetion", then you have *another* problem elsewhere. That's it.
>
> Do me a favor : patch the code of this method, add a try { ... } catch (
> ArrayOutOfBoundException e) { e.printStackTrace(); } in it, and if the
> stacktrace is produced, I own you a beer, ok ?
>
> Thanks.
> Emmanuel.
>
> PS : Chris fixed the bug 3 months ago. I applied the patch. Twice.
>
>
>
Re: [jira] Commented: (DIRSERVER-970) Hot Partition Fails With ArrayIndexOutOfBoundsException
Posted by Emmanuel Lecharny <el...@apache.org>.
Ole Ersoy a écrit :
>
>
> Emmanuel Lecharny wrote:
>
>> Ole Ersoy a écrit :
>>
>>> Emmanuel,
>>>
>>>
>>> Suppose I was using an old jar. Why does my test pass then?
>>
>>
>> I told you three times that the bug happens ONLY if you run the test
>> with a log4j in DEBUG mode, otherwise the toString() method is
>> _never_ called. This is why your test pass when you don't use the
>> logging file.
>
>
> I think this is what you are missing.
> ========================================================================
> This is why your test pass when you don't use the logging file.
> ========================================================================
>
> I am using the logging file. It's only if the logging file is renamed
> or removed that the exception happens.
Oh, ok. I inverted the context. Nevertheless, this toString() method is
only called when in DEBUG mode. So this is not something you are likely
to have, unless you are in DEBUG mode.
> I gave the verification process. We've spent way more time discussing
> this than it would have taken you to just run through the verification
> steps. If you tell me that renaming the logging file should cause
> this exception, then I'll close the issue.
I'm not telling that shooting the messenger (here, the logging file)
will help at all. I just say that - and if you look carefully at the
code I posted - this is definitively *not* a code in the trunk, as it
has been fixed.
Look at the line 320, and simply tell me if this can throw the exception
or not. If the response is :"yes, this is strange, it should not but I
get the excpetion", then you have *another* problem elsewhere. That's it.
Do me a favor : patch the code of this method, add a try { ... } catch (
ArrayOutOfBoundException e) { e.printStackTrace(); } in it, and if the
stacktrace is produced, I own you a beer, ok ?
Thanks.
Emmanuel.
PS : Chris fixed the bug 3 months ago. I applied the patch. Twice.
Re: [jira] Commented: (DIRSERVER-970) Hot Partition Fails With ArrayIndexOutOfBoundsException
Posted by Ole Ersoy <ol...@gmail.com>.
Emmanuel Lecharny wrote:
> Ole Ersoy a écrit :
>
>> Emmanuel,
>>
>>
>> Suppose I was using an old jar. Why does my test pass then?
>
> I told you three times that the bug happens ONLY if you run the test
> with a log4j in DEBUG mode, otherwise the toString() method is _never_
> called. This is why your test pass when you don't use the logging file.
I think this is what you are missing.
========================================================================
This is why your test pass when you don't use the logging file.
========================================================================
I am using the logging file. It's only if the logging file is renamed or removed that the exception happens. I gave the verification process. We've spent way more time discussing this than it would have taken you to just run through the verification steps. If you tell me that renaming the logging file should cause this exception, then I'll close the issue.
SNIP
Cheers,
- Ole
Re: [jira] Commented: (DIRSERVER-970) Hot Partition Fails With ArrayIndexOutOfBoundsException
Posted by Emmanuel Lecharny <el...@apache.org>.
Ole Ersoy a écrit :
> Emmanuel,
>
>
> Suppose I was using an old jar. Why does my test pass then?
I told you three times that the bug happens ONLY if you run the test
with a log4j in DEBUG mode, otherwise the toString() method is _never_
called. This is why your test pass when you don't use the logging file.
> It only fails if I rename the logging file. So that means that
> somehow renaming the logging file tells the class loader to load from
> a different jar. Does that make sense?
No, this is non-sense. Read my responses.
>
> You understand this better than I do. All I understand is that if I
> rename the logging file, I get the exception. As long as the logging
> file is there, everyone is happy. So if you think this is fine, then
> we can close the issue.
I expect you to close this issue, you opened it ! And you won't be happy
until you find the reason...
Emmanuel.
PS: I suggest you stop debugging the test for a while, keep it somewhere
aside, and have a good sleep. Tomorrow you will be fresh, and suddenly
under your shower you will understand what happens.
Re: [jira] Commented: (DIRSERVER-970) Hot Partition Fails With ArrayIndexOutOfBoundsException
Posted by Ole Ersoy <ol...@gmail.com>.
Emmanuel,
Suppose I was using an old jar. Why does my test pass then? It only fails if I rename the logging file. So that means that somehow renaming the logging file tells the class loader to load from a different jar. Does that make sense?
You understand this better than I do. All I understand is that if I rename the logging file, I get the exception. As long as the logging file is there, everyone is happy. So if you think this is fine, then we can close the issue.
Cheers,
- Ole
Emmanuel Lecharny wrote:
> Ole Ersoy a écrit :
>
>> Well - It's really no big deal. We can leave it for later. I spent
>> half a day debugging this, because it's so bizarre. Honestly I
>> cleaned out my maven repository twice. Rebuilt ADS. Everything in my
>> repository is fresh.
>
>
> It 's not enough... *if* at least one of the jars you are using use a
> old version of the shared-ldap jar, then you are dead. You can clean
> your repo as meny time as you want, it won't change at all the behaviour
> of your code. Just check your pom.xml, the problem is there.
>
>> As long as the logging file is present, life is good.
>
> Plain normal. The problem is due to a debug section : the debug code
> call toString().
>
>>
>> There's definitely something going on though. Why does renaming a
>> logging file cause that exception?
>
> Because you are running it in DEBUG mode. Switch to WARN, it will be ok.
> But it won't fix your pom.xml...
>
>> I'll put some simple instructions in the JIRA for verification.
>
> Just verify your pom. It should be ok
>
> Emmanuel
>
>
Re: [jira] Commented: (DIRSERVER-970) Hot Partition Fails With ArrayIndexOutOfBoundsException
Posted by Emmanuel Lecharny <el...@apache.org>.
Ole Ersoy a écrit :
> Well - It's really no big deal. We can leave it for later. I spent
> half a day debugging this, because it's so bizarre. Honestly I
> cleaned out my maven repository twice. Rebuilt ADS. Everything in my
> repository is fresh.
It 's not enough... *if* at least one of the jars you are using use a
old version of the shared-ldap jar, then you are dead. You can clean
your repo as meny time as you want, it won't change at all the behaviour
of your code. Just check your pom.xml, the problem is there.
> As long as the logging file is present, life is good.
Plain normal. The problem is due to a debug section : the debug code
call toString().
>
> There's definitely something going on though. Why does renaming a
> logging file cause that exception?
Because you are running it in DEBUG mode. Switch to WARN, it will be ok.
But it won't fix your pom.xml...
> I'll put some simple instructions in the JIRA for verification.
Just verify your pom. It should be ok
Emmanuel
Re: [jira] Commented: (DIRSERVER-970) Hot Partition Fails With ArrayIndexOutOfBoundsException
Posted by Ole Ersoy <ol...@gmail.com>.
Well - It's really no big deal. We can leave it for later. I spent half a day debugging this, because it's so bizarre. Honestly I cleaned out my maven repository twice. Rebuilt ADS. Everything in my repository is fresh. As long as the logging file is present, life is good.
There's definitely something going on though. Why does renaming a logging file cause that exception? I'll put some simple instructions in the JIRA for verification.
Cheers,
- Ole
Emmanuel Lecharny wrote:
> Here is the code where you have the exception :
> /**
> * Gets the String for the OID of this SchmeaObject.
> *
> * @return the OID of this SchmeaObject
> */
> public String toString()
> {
> return "<" + oid + ", " + ( ( names == null ) || (
> names.length == 0 ) ? "null" : names[0] ) + ">";
> }
>
> Line 320 is the "return blah..."
>
> Look at it, it's directly taken from trunk, rel 529404, and tell me if
> you can simply have a ArrayIndexOutOfBoundsException here.
>
> Trust me, we have fixed this bug, and this is not the code your are
> testing, take it for granted.
>
> I can spend 5 minutes on your test, but it will work on my computer,
> at least it won't fail on line 320 if this class.
>
> It's like in court : evidences of guilt should be brought by the
> prosecutor, the defender should not proof his innocence ;)
>
> Emmanuel
>
> I may spend some time on your issue, but not right now... I'm pretty
> busy atm. Better if you try to find where in your build you have a
> pb...
>
>
> On 6/15/07, Ole Ersoy <ol...@gmail.com> wrote:
>> Emmanuel,
>>
>> I already double checked all the things you are suspicious of.
>> Honestly. I have the tests running fine in the project. If I rename
>> the logging configuration file, that's the exception that's thrown.
>> It should take you roughly half a minute to verify.
>>
>> Cheers,
>> - Ole
>>
>>
>>
>> Emmanuel Lecharny wrote:
>> > Ersin Er a écrit :
>> >
>> >> [OT]
>> >>
>> >> Please keep Jira conversations in Jira, not on the dev list.
>> >
>> > Ersin, the JIRA has been closed, then repopened, but should be closed
>> > again, so I think this convo is better suited into the dev list,
>> > otherwise we will have a never ending JIRA :)
>> >
>> > IMHO.
>> >
>>
>
>
Re: [jira] Commented: (DIRSERVER-970) Hot Partition Fails With ArrayIndexOutOfBoundsException
Posted by Emmanuel Lecharny <el...@gmail.com>.
Here is the code where you have the exception :
/**
* Gets the String for the OID of this SchmeaObject.
*
* @return the OID of this SchmeaObject
*/
public String toString()
{
return "<" + oid + ", " + ( ( names == null ) || (
names.length == 0 ) ? "null" : names[0] ) + ">";
}
Line 320 is the "return blah..."
Look at it, it's directly taken from trunk, rel 529404, and tell me if
you can simply have a ArrayIndexOutOfBoundsException here.
Trust me, we have fixed this bug, and this is not the code your are
testing, take it for granted.
I can spend 5 minutes on your test, but it will work on my computer,
at least it won't fail on line 320 if this class.
It's like in court : evidences of guilt should be brought by the
prosecutor, the defender should not proof his innocence ;)
Emmanuel
I may spend some time on your issue, but not right now... I'm pretty
busy atm. Better if you try to find where in your build you have a
pb...
On 6/15/07, Ole Ersoy <ol...@gmail.com> wrote:
> Emmanuel,
>
> I already double checked all the things you are suspicious of. Honestly. I have the tests running fine in the project. If I rename the logging configuration file, that's the exception that's thrown. It should take you roughly half a minute to verify.
>
> Cheers,
> - Ole
>
>
>
> Emmanuel Lecharny wrote:
> > Ersin Er a écrit :
> >
> >> [OT]
> >>
> >> Please keep Jira conversations in Jira, not on the dev list.
> >
> > Ersin, the JIRA has been closed, then repopened, but should be closed
> > again, so I think this convo is better suited into the dev list,
> > otherwise we will have a never ending JIRA :)
> >
> > IMHO.
> >
>
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
Re: [jira] Commented: (DIRSERVER-970) Hot Partition Fails With ArrayIndexOutOfBoundsException
Posted by Ole Ersoy <ol...@gmail.com>.
Emmanuel,
I already double checked all the things you are suspicious of. Honestly. I have the tests running fine in the project. If I rename the logging configuration file, that's the exception that's thrown. It should take you roughly half a minute to verify.
Cheers,
- Ole
Emmanuel Lecharny wrote:
> Ersin Er a écrit :
>
>> [OT]
>>
>> Please keep Jira conversations in Jira, not on the dev list.
>
> Ersin, the JIRA has been closed, then repopened, but should be closed
> again, so I think this convo is better suited into the dev list,
> otherwise we will have a never ending JIRA :)
>
> IMHO.
>
Re: [jira] Commented: (DIRSERVER-970) Hot Partition Fails With ArrayIndexOutOfBoundsException
Posted by Emmanuel Lecharny <el...@apache.org>.
Ersin Er a écrit :
> [OT]
>
> Please keep Jira conversations in Jira, not on the dev list.
Ersin, the JIRA has been closed, then repopened, but should be closed
again, so I think this convo is better suited into the dev list,
otherwise we will have a never ending JIRA :)
IMHO.
Re: [jira] Commented: (DIRSERVER-970) Hot Partition Fails With ArrayIndexOutOfBoundsException
Posted by Ersin Er <er...@gmail.com>.
[OT]
Please keep Jira conversations in Jira, not on the dev list.
On 6/15/07, Ole Ersoy <ol...@gmail.com> wrote:
> Emmanuel,
>
> I know - It totally seems like I just need to switch to a more recent version. This one really tricked me up, because first I cleared out my Maven Repository. Then rebuilt ADS again. Then tested the archetype classes. The tests run fine. So finally I'm ready to get back to work on the DAS. I copy the Embedded test classes over to that project, run them, and get the exception. #%^$#$$^$. So I thought maybe there was something weird going on with the project setup. So I clean out the maven repository again, rebuild ADS again, create a brand new project, copy the archetype test packages over to the new project, run the tests...voila...same exception. So finally I remembered that I needed to copy the logging properties over as well. Then everything runs smooth.
>
> OK - I have everything running fine. Here's what I'm going to do. I'll rename the logging properties file and run the test again. Here is the stack trace:
>
> 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:103)
> 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.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
> at org.apache.directory.apacheds.testing.setup.ADSEmbeddedConnectionTemplate.connect(ADSEmbeddedConnectionTemplate.java:126)
> at org.apache.directory.apacheds.testing.setup.ADSEmbeddedConnectionTemplateTest.testSchemaConnect(ADSEmbeddedConnectionTemplateTest.java:42)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at junit.framework.TestCase.runTest(TestCase.java:154)
> at junit.framework.TestCase.runBare(TestCase.java:127)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:118)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
>
> Strange right?
>
> Cheers,
> - Ole
>
>
>
> Emmanuel Lecharny (JIRA) wrote:
> > [ https://issues.apache.org/jira/browse/DIRSERVER-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505359 ]
> >
> > Emmanuel Lecharny commented on DIRSERVER-970:
> > ---------------------------------------------
> >
> > Ole,
> >
> > can you paste teh stack trace ?
> >
> > if you get the same :
> > ava.lang.ArrayIndexOutOfBoundsException: 0
> > at org.apache.directory.shared.ldap.schema.AbstractSchemaObject.toString(AbstractSchemaObject.java:320)
> >
> > then consider the bug fixed. Just switch to the most recent version of the trunk.
> >
> >> Hot Partition Fails With ArrayIndexOutOfBoundsException
> >> -------------------------------------------------------
> >>
> >> Key: DIRSERVER-970
> >> URL: https://issues.apache.org/jira/browse/DIRSERVER-970
> >> Project: Directory ApacheDS
> >> Issue Type: Bug
> >> Reporter: Ole Ersoy
> >> Attachments: IndependentHotPartitionTest.java
> >>
> >>
> >> After building the ApacheDS trunk on my machine, I started getting strange results when running tests. So I cleaned out the Maven repository completely, rebuilt ADS, and started from scratch. Now when I try to run the attached test (Needs a running server), I get this:
> >> 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:103)
> >> 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.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
> >> at org.apache.tuscany.das.ldap.learning.test.IndependentHotPartitionTest.createDASPartition(IndependentHotPartitionTest.java:80)
> >> at org.apache.tuscany.das.ldap.learning.test.IndependentHotPartitionTest.testCreateDASPartition(IndependentHotPartitionTest.java:30)
> >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> >> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> >
>
--
Ersin Er
R.A. and Ph.D Student at the Dept. of Computer Eng. in Hacettepe University
http://www.cs.hacettepe.edu.tr
Committer and PMC Member of The Apache Directory Project
http://directory.apache.org
Re: [jira] Commented: (DIRSERVER-970) Hot Partition Fails With ArrayIndexOutOfBoundsException
Posted by Emmanuel Lecharny <el...@apache.org>.
Ole Ersoy a écrit :
> Emmanuel,
>
> I know - It totally seems like I just need to switch to a more recent
> version. This one really tricked me up, because first I cleared out
> my Maven Repository. Then rebuilt ADS again. Then tested the
> archetype classes. The tests run fine. So finally I'm ready to get
> back to work on the DAS. I copy the Embedded test classes over to
> that project, run them, and get the exception. #%^$#$$^$. So I
> thought maybe there was something weird going on with the project
> setup. So I clean out the maven repository again, rebuild ADS again,
> create a brand new project, copy the archetype test packages over to
> the new project, run the tests...voila...same exception. So finally I
> remembered that I needed to copy the logging properties over as well.
> Then everything runs smooth.
This is because you run it in WARN mode, when we don't call the
toString() method.
>
>
> OK - I have everything running fine. Here's what I'm going to do.
> I'll rename the logging properties file and run the test again. Here
> is the stack trace:
>
> java.lang.ArrayIndexOutOfBoundsException: 0
> at
> org.apache.directory.shared.ldap.schema.AbstractSchemaObject.toString(AbstractSchemaObject.java:320)
>
This has been fixed. Really. The
java.lang.ArrayIndexOutOfBoundsException was due to a bad access to an
empty ArrayList, and the toString method is now doing :
if ( ( name == null ) || ( name.size() == 0 ) ) then print "null" else
print name [0]
There is no case this can cause a AIOOBE. You can look at the code,
there is no magic in it
>
> Strange right?
Yes, strange. Now, my guess : in your pom.xml, you are refering an old
version of this jar, or refering another jar which refers this old version.
What you can do is to setup a BP on the faultive method, and debug the
code to see what happens...
Emmanuel
Re: [jira] Commented: (DIRSERVER-970) Hot Partition Fails With ArrayIndexOutOfBoundsException
Posted by Ole Ersoy <ol...@gmail.com>.
Emmanuel,
I know - It totally seems like I just need to switch to a more recent version. This one really tricked me up, because first I cleared out my Maven Repository. Then rebuilt ADS again. Then tested the archetype classes. The tests run fine. So finally I'm ready to get back to work on the DAS. I copy the Embedded test classes over to that project, run them, and get the exception. #%^$#$$^$. So I thought maybe there was something weird going on with the project setup. So I clean out the maven repository again, rebuild ADS again, create a brand new project, copy the archetype test packages over to the new project, run the tests...voila...same exception. So finally I remembered that I needed to copy the logging properties over as well. Then everything runs smooth.
OK - I have everything running fine. Here's what I'm going to do. I'll rename the logging properties file and run the test again. Here is the stack trace:
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:103)
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.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
at org.apache.directory.apacheds.testing.setup.ADSEmbeddedConnectionTemplate.connect(ADSEmbeddedConnectionTemplate.java:126)
at org.apache.directory.apacheds.testing.setup.ADSEmbeddedConnectionTemplateTest.testSchemaConnect(ADSEmbeddedConnectionTemplateTest.java:42)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
Strange right?
Cheers,
- Ole
Emmanuel Lecharny (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/DIRSERVER-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505359 ]
>
> Emmanuel Lecharny commented on DIRSERVER-970:
> ---------------------------------------------
>
> Ole,
>
> can you paste teh stack trace ?
>
> if you get the same :
> ava.lang.ArrayIndexOutOfBoundsException: 0
> at org.apache.directory.shared.ldap.schema.AbstractSchemaObject.toString(AbstractSchemaObject.java:320)
>
> then consider the bug fixed. Just switch to the most recent version of the trunk.
>
>> Hot Partition Fails With ArrayIndexOutOfBoundsException
>> -------------------------------------------------------
>>
>> Key: DIRSERVER-970
>> URL: https://issues.apache.org/jira/browse/DIRSERVER-970
>> Project: Directory ApacheDS
>> Issue Type: Bug
>> Reporter: Ole Ersoy
>> Attachments: IndependentHotPartitionTest.java
>>
>>
>> After building the ApacheDS trunk on my machine, I started getting strange results when running tests. So I cleaned out the Maven repository completely, rebuilt ADS, and started from scratch. Now when I try to run the attached test (Needs a running server), I get this:
>> 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:103)
>> 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.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
>> at org.apache.tuscany.das.ldap.learning.test.IndependentHotPartitionTest.createDASPartition(IndependentHotPartitionTest.java:80)
>> at org.apache.tuscany.das.ldap.learning.test.IndependentHotPartitionTest.testCreateDASPartition(IndependentHotPartitionTest.java:30)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>
[jira] Commented: (DIRSERVER-970) Hot Partition Fails With
ArrayIndexOutOfBoundsException
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12505359 ]
Emmanuel Lecharny commented on DIRSERVER-970:
---------------------------------------------
Ole,
can you paste teh stack trace ?
if you get the same :
ava.lang.ArrayIndexOutOfBoundsException: 0
at org.apache.directory.shared.ldap.schema.AbstractSchemaObject.toString(AbstractSchemaObject.java:320)
then consider the bug fixed. Just switch to the most recent version of the trunk.
> Hot Partition Fails With ArrayIndexOutOfBoundsException
> -------------------------------------------------------
>
> Key: DIRSERVER-970
> URL: https://issues.apache.org/jira/browse/DIRSERVER-970
> Project: Directory ApacheDS
> Issue Type: Bug
> Reporter: Ole Ersoy
> Attachments: IndependentHotPartitionTest.java
>
>
> After building the ApacheDS trunk on my machine, I started getting strange results when running tests. So I cleaned out the Maven repository completely, rebuilt ADS, and started from scratch. Now when I try to run the attached test (Needs a running server), I get this:
> 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:103)
> 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.ldap.InitialLdapContext.<init>(InitialLdapContext.java:134)
> at org.apache.tuscany.das.ldap.learning.test.IndependentHotPartitionTest.createDASPartition(IndependentHotPartitionTest.java:80)
> at org.apache.tuscany.das.ldap.learning.test.IndependentHotPartitionTest.testCreateDASPartition(IndependentHotPartitionTest.java:30)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.