[
https://issues.apache.org/jira/browse/LOG4J2-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107366#comment-13107366
]
Ralph Goers commented on LOG4J2-48:
-----------------------------------
I have corrected the Log4j 2.0 and SLF4J bridge to properly pass the throwable
from ParameterizedMessage so that it is included in the LogEvent and will now
be properly logged, so the actual defect being raised here has been resolved.
Whether to include the Throwable in the Message interface or create a new
ThrowableMessage is a separate topic that should be in its own Jira issue.
> Throwables in ParameterizedMessage
> ----------------------------------
>
> Key: LOG4J2-48
> URL: https://issues.apache.org/jira/browse/LOG4J2-48
> Project: Log4j 2
> Issue Type: Bug
> Components: API
> Affects Versions: 0.1
> Reporter: John Vasileff
> Fix For: 0.1
>
> Attachments:
> 0001-add-throwable-to-Message-objects-remove-from-log-met.patch
>
>
> ParameterizedMessage objects are capable of identifying throwables when
> provided as the last parameter in methods like:
> void info(String message, Object... params);
> but they are not properly logged. In addition, for some Logger methods, a
> throwable may be specified more than once for Message types that support
> throwables:
> void info(Message msg, Throwable t);
> See
> http://mail-archives.apache.org/mod_mbox/logging-log4j-dev/201109.mbox/%3cddc2e2a0-a4ba-4ed4-8f05-378152690...@gmail.com%3e
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
