log4j? Create your own appender that doesn't do that.
Thank you for your response. Unfortunatly this does not help me much.
How could I 're-write' the Console appender so that it does nog print all these (long) stacktraces.
I think this has somehow to do with how JBoss wrappes exceptions....
Can somebody give a hint?
When searching for errors, I really like to see the whole stacktrace, so I am really glad that every exception has it's cause and is not masking the real error cause.
Genman's idea isn't so bad and I think it shouldn't be too difficult to write your own ConsoleAppender (at first glance ;-)
Just inherit from the log4j ConsoleAppender, overwrite append(LoggingEvent), do you own thing when there is a throwableInfo or let the superclass do everything if not.