[
https://issues.apache.org/jira/browse/LOG4J2-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Williams resolved LOG4J2-475.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.0-rc1
Fixed with r1565889. Based it off of Matt's patch, but there's no need to also
have a decoding hook because the appender doesn't read events, it only writes
them.
> MongoDBConnection is broken because it uses addDecodingHook instead of
> addEncodingHook
> --------------------------------------------------------------------------------------
>
> Key: LOG4J2-475
> URL: https://issues.apache.org/jira/browse/LOG4J2-475
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.0-beta9
> Reporter: Tal Liron
> Assignee: Nick Williams
> Fix For: 2.0-rc1
>
> Attachments: 0001-Fix-LOG4J2-475.patch
>
>
> Seems trivial to fix, just use addEncodingHook.
> (I have a feeling MongoDB logging has never been tested! Is there a unit test
> for it?)
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
