yeah, this issue was caused by multithreaded output being intervleaved.
i'm still not happy with processing exception strings though. i'd prefer
we did some kind of folding of exceptions using javascript on the wicket
exception page and not alter the exception at all. but that can wait until
n
i dont think so because you do get "Caused by"?
We don't print caused by, that is the thing we change about the input.
what do you exactly see? so whats in that [...] space you have in the email?
johan
On 6/20/07, Jonathan Locke <[EMAIL PROTECTED]> wrote:
could this be caused by this thre
could this be caused by this thread (which we never quite did finish)?
http://www.nabble.com/abbreviated-stack-traces-tf3837742.html#a10899418
Jonathan Locke wrote:
>
> i just got another missing stack trace problem:
>
> [...]
> Caused by: java.lang.NullPointerException
>
> then no stack tr
i just got another missing stack trace problem:
[...]
Caused by: java.lang.NullPointerException
then no stack trace for the NPE. eelco earlier asserted that my logging
config must be wrong while johan said we must have a problem. the only odd
bit of configuration in our log4j file is this patt
