Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Users List" <log4j-user@logging.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=dk20050327; d=earthlink.net;
  b=TFwjjZhfCcmSdkqBeGALzBGJHFpmb6aGtMPsW0zei1lNQCdrSbqBdsm9QIWG2DSd;
  h=Received:From:Organization:To:Subject:Date:User-Agent:References:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id:X-ELNK-Trace:X-Originating-IP;
From: Tim Watts <timtw@earthlink.net>
Organization: Clifton Farm
To: log4j-user@logging.apache.org
Subject: Re: Suppressing stacktrace output
Date: Thu, 20 Mar 2008 10:40:56 -0400
User-Agent: KMail/1.9.5
References: <16145551.post@talk.nabble.com> <16168549.post@talk.nabble.com>
 <5e87acee0803200215q2fe91e2laad561a6c4e5a28e@mail.gmail.com>
In-Reply-To: <5e87acee0803200215q2fe91e2laad561a6c4e5a28e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200803201040.56494.timtw@earthlink.net>


OR subclass PatternLayout and add a setIgnoresThrowable(). Then use this 
subclass in your console appender definition and add a property to disable:

	...
	log4j.appender.console.layout=com.mydomain.MyPatternLayout
	log4j.appender.console.layout.IgnoresThrowable=false
	...

(or whatever the XML equivalent is)

This approach would allow you to apply this behaviour to other appenders if 
you wanted to later.

On Thursday 20 March 2008 5:15 am, Maarten Bosteels wrote:
> see
> http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Layout.html#ig
>noresThrowable()
>
> "If the layout handles the throwable object contained within LoggingEvent,
> then the layout should return false. Otherwise, if the layout ignores
> throwable object, then the layout should return true. The SimpleLayout,
> TTCCLayout, PatternLayout all return true. The XMLLayout returns false."
>
> For appenders that extend WriterAppender, the stacktrace will be appended
> by the WriterAppender
> when the layout ignores the throwable.
>
> see
> http://logging.apache.org/log4j/1.2/xref/org/apache/log4j/WriterAppender.ht
>ml#300
>
> So I guess you could extend ConsoleAppender and override subAppend.
>
> regards,
> Maarten
>
> On Thu, Mar 20, 2008 at 1:26 AM, jimski <jimkski@gmail.com> wrote:
> > Hi James-
> >
> >
> > I think the layout determines if the stack trace is logged.  How are
> > you configuring the console appender?
> >
> >
> > I thought so too.  But it doesn't seem that's the case.  I'm using the
> > following pattern:
> >
> > [%d{yyyy-MM-dd HH:mm:ss}] %-5p %m %n
> >
> > so I expect only a date, the level, the message and a newline character.
> >
> > --
> > View this message in context:
> > http://www.nabble.com/Suppressing-stacktrace-output-tp16145551p16168549.h
> >tml Sent from the Log4j - Users mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-user-help@logging.apache.org

-- 
"Absolute security comes with chains."

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org