logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (LOG4J2-1282) Make RingBufferLogEvent::mergePropertiesIntoContextMap allocation-free if possible
Date Sat, 02 Apr 2016 00:39:25 GMT

     [ https://issues.apache.org/jira/browse/LOG4J2-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Remko Popma closed LOG4J2-1282.
-------------------------------
    Resolution: Duplicate

Closing this issue. Superceded by LOG4J2-1349.

> Make RingBufferLogEvent::mergePropertiesIntoContextMap allocation-free if possible
> ----------------------------------------------------------------------------------
>
>                 Key: LOG4J2-1282
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1282
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.5
>            Reporter: Remko Popma
>
> RingBufferLogEvent::mergePropertiesIntoContextMap is called in the background (consumer)
thread for each event.
> If configuration properties are specified it allocates the following temporary objects:
> * make mutable copy of the ThreadContext map
> * iterator over configuration properties map
> * for config values containing ${} placeholders, call {{StrSubstitutor.replace}} (which
creates multiple temporary objects)
> (If configuration properties are not specified, no temporary objects are allocated.)



--
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


Mime
View raw message