Does JBoss log RuntimeExceptions in a reasonable way?

roland.kofler Sep 6, 2006 1:23 PM

I guess most experienced people in java agree that RuntimeExceptions represent Errors, while Checked Exceptions represents a sort of return values.
A Container like JBoss should catch application errors aka RuntimeExceptions at some point and log them away. So application developers like me can follow the stacktrace and find/ debug the cause of the error.
Jboss does behave like this, but with a big drawback: it logs only the RuntimeExceptions Message, NOT the full stacktrace! Thus rendering the logfile analysis mostly useless.
Does anybody know the reason JBoss behaves like this and if there exists a remedy?

1. Re: Does JBoss log RuntimeExceptions in a reasonable way?

peterj Sep 6, 2006 1:31 PM (in response to roland.kofler)

What I always see is an exception with a stack trace, followed by a 'caused by exception' with a stack trace, and so on. Usually the initial runtime exception is part of the last 'caused by exception' clause. Perhaps if you provide a particular instance where only the message printed, that would help.
Actions
2. Re: Does JBoss log RuntimeExceptions in a reasonable way?

roland.kofler Sep 6, 2006 2:25 PM (in response to roland.kofler)

Peter your right, I mad the tests you suggested. Sometimes we log.error(e); wich gives back only the exception message. this seams to be my fault. thanks for helping in clarifying
Actions

Go to original post