You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2004/08/02 23:08:03 UTC
DO NOT REPLY [Bug 30440] New: -
logger.smething(exception) does not log stack trace
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30440>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30440
logger.smething(exception) does not log stack trace
Summary: logger.smething(exception) does not log stack trace
Product: Log4j
Version: 1.0
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Other
Component: Other
AssignedTo: log4j-dev@jakarta.apache.org
ReportedBy: yozh@mx1.ru
Hello, I have I wish.
logger.debug(exception)
(or logger.info(exception))
behaves as
logger.debug(exception.toString())
but should (I think) be equlivalent of
logger.debug(exception.getMessage(), exception)
to get exception stack trace in logs. Because exceptions mostly logged to help
debugging, and in this case, stack trace can help.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org