I gave this one a try. Go in a loop while trying to print a stack
trace, in case of an exception, set is as the effective exception, and
retry. Though when I started thinking more about this. I need to
repeat the same for class name, file name, line number, etc. Though
all these are independent res
Stacktraces need to provide value, otherwise they just waste log space. So
whether or not a stack trace should be printed should be based on whether it is
going to provide value or not. Otherwise, just logging the exception message
and class would be fine.
Remember, the original message was goi
Hello,
Yesterday I've paged by a colleague for a really strange logging
behaviour on production. The logging stops working after 15m-2h.
Diving into Tomcat catalina logs pointed out that there is a
particular exception whose Throwable#printStackTrace(PrintWriter)
method is throwing an exception --
