I don't recall ever seeing Log4j cut off stack traces. In fact, the reason
the FilteredPatternLayout [1] was invented was because stack traces contained
too much detail, not too little.
Unless someone else can confirm that Log4j is the culprit, I would look
elsewhere to find who/what might be cutting off stack frames.
[1] http://openutils.sourceforge.net/openutils-log4j/filteredlayout.html
Jake
On Thu, 11 Feb 2010 00:08:18 -0500
Godmar Back <[email protected]> wrote:
Hi,
I'm trying to find out how to configure log4j to not cut off crucial
parts of stack traces.
Here is an example from my Apache Tomcat log:
com.thoughtworks.xstream.mapper.CannotResolveClassException: WallPosting :
WallPosting
at
com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:68)
at
com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
at
com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:71)
at
com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:38)
at
com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88)
...
In order to debug this problem, I need to see the full stack trace,
but I can't find how to configure log4j accordingly.
All I've found so far are users similarly confused as I am (*)
I'm not even sure if log4j is the culprit or not.
Thanks!
- Godmar
Google keywords: log4j, stacktrace, stack trace, truncation,
truncated, cut off, ellipsis, short stack trace
(*)
http://www.velocityreviews.com/forums/t147237-log4j-stack-trace-depth.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
