views:

63

answers:

4

I want to log only the first few lines of Exceptions in my program. I know, I can do something like this to print only the first 5 lines of a stacktrace:

Throwable e = ...;
StackTraceElement[] stack = e.getStackTrace();
int maxLines = (stack.length > 4) ? 5 : stack.length;
for (int n = 0; n < maxLines; n++) {
    System.err.println(stack[n].toString());
}

But I would rather use log4j (or sl4j over log4j to be more precise) for logging. Is there a way to tell log4j that it should only print the first 5 lines of a stacktrace?

+4  A: 

You can use a EnhancedPatternLayout in log4j to format your stacktraces.

See http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/EnhancedPatternLayout.html, specifically the section about the "throwable" pattern in the pattern table.

Note that support for the %throwable{n} support is rather new and requires at least log4j 1.2.16 (which is the latest at time of writing)

For tracking purposes, this is the ticket that dealt with its implementation: https://issues.apache.org/bugzilla/show_bug.cgi?id=48902

Hendrik
wonderful, %throwable{5} does just what i need.
deadsven
+1  A: 

I don't know of such an option. But you can extend your current appender (for example RollingFileAppender) and provide an append / doAppend / subAppend method (depending on which class you are extending) to handle this.

The throwable information is contained in LoggingEvent.throwableInformation

That said, I'm not sure you should do this - you can lose important information that way.

Bozho
+1  A: 

Yup... EnhancedPatternLayout provides this functionality.

For a log4j config of

<appender name="Console" class="org.apache.log4j.ConsoleAppender">
    <param name="Threshold" value="debug"/>
    <layout class="org.apache.log4j.EnhancedPatternLayout">
        <param name="ConversionPattern" value="%d %-5p [%t] %c.%M - %m%n %throwable{short}"/>
    </layout>
</appender>

and for a piece of Java code like

throw new Exception(new Exception("Inner Exception"));

You get the following in the log file...

java.lang.Exception: java.lang.Exception: Inner Exception

If we remove the '%throwable{short}' from our log4j config file we would get the full stack trace

deepak
+1  A: 

Yes, it is part of log4j since log4j 1.2.16

Here is the original proposal in the Apache issue tracker that describes in detail how each of the applications of the %throwable pattern looks like: https://issues.apache.org/bugzilla/show_bug.cgi?id=48902#c0

bunting