[
https://issues.apache.org/jira/browse/LOG4J2-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15659156#comment-15659156
]
Remko Popma commented on LOG4J2-1688:
-------------------------------------
I'll take a look at this. I think this is related to how LOG4J2-1342 was
addressed.
If you're looking for a workaround, either switching off asynchronous logging
or switching off garbage-free logging (set system property
{{log4j2.enable.threadlocals}} to {{false}}) should result in the parameter
array being preserved.
> Multiple loggings of arguments are setting these arguments to null
> ------------------------------------------------------------------
>
> Key: LOG4J2-1688
> URL: https://issues.apache.org/jira/browse/LOG4J2-1688
> Project: Log4j 2
> Issue Type: Bug
> Affects Versions: 2.7
> Reporter: Stefan Hammelbeck
>
> We are using SLF4J over log4j Version 2.7.
> Calling {{org.slf4j.Logger.error(someFormat, args)}} *twice* with an
> {{Object[] args}} causes all elements of {{args}} to be set to {{null}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
