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 "Ralph Goers (JIRA)" <ji...@apache.org> on 2016/11/08 16:57:59 UTC
[jira] [Issue Comment Deleted] (LOG4J2-1677) (GC) Avoid allocating
temporary objects in MapFilter
[ https://issues.apache.org/jira/browse/LOG4J2-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers updated LOG4J2-1677:
--------------------------------
Comment: was deleted
(was: And now allows the Map to be modified? If so, please revert.
The contents of LogEvents are not supposed to be allowed to be modified by components once they are passed to the Logger to be logged. Allowing a Filter or an Appender to modify the contents means that other Appenders will see the modification if they get LogEvent later in the processing. We don't allow that. Instead, a copy of the LogEvent must be made for use by that Appender or components derived from it.)
> (GC) Avoid allocating temporary objects in MapFilter
> ----------------------------------------------------
>
> Key: LOG4J2-1677
> URL: https://issues.apache.org/jira/browse/LOG4J2-1677
> Project: Log4j 2
> Issue Type: Improvement
> Components: Filters
> Affects Versions: 2.7
> Reporter: Remko Popma
> Assignee: Remko Popma
> Fix For: 2.8
>
>
> Make MapFilter garbage-free.
--
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