directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ole Ersoy <>
Subject Re: [jira] Commented: (DIRSERVER-970) Hot Partition Fails With ArrayIndexOutOfBoundsException
Date Fri, 15 Jun 2007 22:10:23 GMT

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.

- 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

View raw message