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 "Greg Thomas (JIRA)" <ji...@apache.org> on 2016/03/08 14:56:40 UTC
[jira] [Commented] (LOG4J2-1309) Configuration file error does not
show cause exception
[ https://issues.apache.org/jira/browse/LOG4J2-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184931#comment-15184931 ]
Greg Thomas commented on LOG4J2-1309:
-------------------------------------
I'm probably being a bit dense here, but by my reading of the constructor javadoc - [https://logging.apache.org/log4j/2.x/log4j-api/apidocs/org/apache/logging/log4j/message/ParameterizedMessage.html#ParameterizedMessage(java.lang.String,%20java.lang.Object[])] the throwable is returned if it's not used up by the message pattern - so why the need for the change?
> Configuration file error does not show cause exception
> ------------------------------------------------------
>
> Key: LOG4J2-1309
> URL: https://issues.apache.org/jira/browse/LOG4J2-1309
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.5
> Reporter: Gary Gregory
> Assignee: Gary Gregory
> Fix For: 2.6
>
>
> Configuration file error does not show cause exception. Instead you see "Error parsing foo" where foo is the file name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org