[
https://issues.apache.org/jira/browse/LOG4J2-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15185054#comment-15185054
]
Remko Popma commented on LOG4J2-1309:
-------------------------------------
This may be a bug I introduced when I was addressing memory leaks in web apps:
The StatusLogger keeps LogEvents with ParameterizedMessage objects in a ring
buffer. Some of the parameters were things like the LoggerContext. Because of
this strong reference, the Log4j context could not be garbage collected when
the web app was stopped/restarted.
What I did to solve this was create ParameterizedNoReferenceMessageFactory and
use that for the StatusLogger. The implementation of that factory is a bit
simplistic: it creates a SimpleMessage, which means the Throwable object logged
by the StatusLogger can no longer be obtained from the message...
> 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: [email protected]
For additional commands, e-mail: [email protected]
