[
https://issues.apache.org/jira/browse/LOG4J2-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16368591#comment-16368591
]
ASF GitHub Bot commented on LOG4J2-2252:
----------------------------------------
Github user cakofony commented on the issue:
https://github.com/apache/logging-log4j2/pull/148
@rgoers That's exactly what I'd like to do, and it works if threadlocals
are disabled.
However if threadlocals are enabled (the default for non-webapps),
ReusableParameterizedMessage -> MutableLogEvent fails to retain the original
format string. This change fixes that case.
regarding `RFC5424Layout`, `StructuredDataMessage` doesn't implement
`ReusableMessage` and is annotated with `AsynchronouslyFormattable`, so the
original message object is passed along.
> 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
> 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)
