[
https://issues.apache.org/jira/browse/LOG4J2-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377945#comment-16377945
]
ASF subversion and git services commented on LOG4J2-2252:
---------------------------------------------------------
Commit ac614e85e59d9e89033eda703ec43dcd2b2b4fc7 in logging-log4j2's branch
refs/heads/release-2.x from [~ckozak]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=ac614e8 ]
LOG4J2-2252 Reusable LogEvents should pass along the original format string
This allows custom layouts to group logged messages parameterized
values without creating new single-use messages for each event.
This slightly modifies the getFormat implementation of some
message types to avoid doing unnecessary work to load the
format string.
> Reusable events drop the original format string
> -----------------------------------------------
>
> Key: LOG4J2-2252
> URL: https://issues.apache.org/jira/browse/LOG4J2-2252
> Project: Log4j 2
> Issue Type: Bug
> Reporter: Carter Douglas Kozak
> Assignee: Remko Popma
> Priority: Major
>
> MutableLogEvent and RingBufferLogEvent hold references to state from original
> messages, but they currently exclude the value of Message.getFormat().
> I would like to write a custom Layout implementation which is aware of the
> format string and parameters, which doesn't necessarily use the formatted
> message value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
