How to print stack trace of StackOverflowException

it fixes the issue The problem is the %-70m in your Layout. It truncates the message, and therefore does not reach the stacktrace. Use %m as usual instead.
Even Better: Write a custom layout, this will work as you want.

wish of those help How do I print a Groovy stack trace? The Java method, Thread.currentThread().getStackTrace() produces a huge stack trace, including a lot of the Groovy internals. I'm seeing a function called twice from a StreamingMarkupBuilder that looks like it should only be called once and I would like to see why Groovy thinks it should be calling it twice. , Solution:

With these it helps Since May 20, 2011, there is a change in the Log class, such that UnknownHostException exceptions are not printed.

I think the issue was by ths following , System.out.println is buffered whereas error output is not buffered. That means that there is occasionally a delay before you see the results from System.out.println. Exceptions are reported through System.err.println, which is not buffered and so prints immediately.
Try switching your System.out.println statements to System.err.println, and see if the problem resolves.

Does that help Without using additional tools (such as creating memory dump, or using profiling API) you can't do it. While you can use LocalVariableInfo class to list local variables, in order to display the values, you'd need to do it explicitly.