[
https://issues.apache.org/jira/browse/LOG4J2-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers resolved LOG4J2-103.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.0-beta3
Assignee: Ralph Goers
Very good work! The patch was applied in revision 1403125. Please verify and
close.
> Log4jLogEvent proxies ThrowableProxy objects
> --------------------------------------------
>
> Key: LOG4J2-103
> URL: https://issues.apache.org/jira/browse/LOG4J2-103
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0-beta2
> Reporter: Das Archive
> Assignee: Ralph Goers
> Labels: patch, testcase
> Fix For: 2.0-beta3
>
> Attachments: Log4jLogEvent_ThrowableProxy.patch,
> MapRewritePolicyTest.java
>
>
> While verifying LOG4J2-99 I stumbled across another small issue:
> When a Log4jLogEvent is reconstructed (in AsynchAppender, MapRewritePolicy or
> PropertiesRewritePolicy) the ThrowableProxy of the original LogEvent is used
> to construct the new Log4JLogEvent.
> There the ThrowableProxy is proxied again. During this the package resolution
> is repeated (mostly with slightly different result).
> I created a patch for Log4JLogEvent to reuse existing ThrowableProxy objects.
> Best Regards,
> Das
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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
