Skip to main content

server.log does not show full exception traceback

1 reply [Last post]
tmpsa
Offline
Joined: 2010-02-01
Points: 0

How do you configure Glassfish to nottruncate tracebacks in server.log?

When an exception is uncaught, a WARNING message is written to server.log, with a traceback. But when the traceback length exceeds a certain number of lines, the last remaining lines are not written! This is indicated by a final line saying "... 42 more". Very frustrating. A full traceback is often needed to solve a problem.

I believe that this should be a FAQ, but I can't find anything anywhere about it. Not even in the Glassfish Administration Guide. :-/

How do I fix this?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
ss141213
Offline
Joined: 2005-03-30
Points: 0

It's done by underlying Throwable class, not by us. When you see
something like "... 42 more," those are referring to stack frames that's
already printed earlier in the same message by
exception.printStackTrace(), so it actually makes things more readable.

Sahoo
On Thursday 13 December 2012 03:11 PM, forums@java.net wrote:
> How do you configure Glassfish to /not/truncate tracebacks in server.log?
> When an exception is uncaught, a WARNING message is written to
> server.log,
> with a traceback. But when the traceback length exceeds a certain
> number of
> lines, the last remaining lines are not written! This is indicated by
> a final
> line saying "... 42 more". Very frustrating. A full traceback is often
> needed
> to solve a problem. I believe that this should be a FAQ, but I can't find
> anything anywhere about it. Not even in the Glassfish Administration
> Guide.
> :-/ How do I fix this?
>
> --
>
> [Message sent by forum member 'tmpsa']
>
> View Post: http://forums.java.net/node/893193
>
>