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.
