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 (asf.osuosl.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Logging chained Exceptions
Date: Tue, 6 Sep 2005 13:26:23 +0100
Message-ID: <2C89AC11F6D7F9469B7E4A71D8309FFD04D0A3@nemesis.axiom.com>
Thread-Topic: Logging chained Exceptions
Thread-Index: AcWv37yFEkRNutknSQmNXdkZeCkbPwC/UoWg
From: "Keith Hatton" <khatton@axiomsystems.com>
To: "Log4J Users List" <log4j-user@logging.apache.org>

Chained exceptions were only introduced in JDK 1.4, so if there is a
requirement to run on JDK 1.3 (which we do) that might explain it.

Keith


-----Original Message-----
From: James Stauffer [mailto:stauffer.james@gmail.com]=20
Sent: 02 September 2005 18:00
To: Log4J Users List
Subject: Logging chained Exceptions


It appears that when a chained Exception is logged that the cause
Exception isn't logged.  Is that something wrong with log4j or the the
Exception that accepts a cause?

--=20
James Stauffer
Are you good? Take the test at http://www.livingwaters.com/good/

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


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