[
https://issues.apache.org/jira/browse/LOG4J2-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285483#comment-17285483
]
Volkan Yazici commented on LOG4J2-3017:
---------------------------------------
[~cliviu], indeed having a custom {{MessageFactory}} should do the trick. For
the delegate you can use {{ParameterizedMessageFactory}}.
For the records, as far as I can conclude from the discussion so far, we (i.e.,
current maintainers of the project) could not come up with a solution that
would address this issue in a hot-fix. {{log4groovy}} is indeed an interesting
idea that could be considered, but a passionate adventure on its own. These
said, there are good news from the Groovy side! I have poked GROOVY-6360 and
they have managed to land a fix within a day! So, even though it is sad to
admit this as a Log4j maintainer, your chances of getting a new Groovy release
where this {{GString}} problem is fixed is higher than getting a new Log4j
release with a workaround for this problem.
> Groovy logging of GString with $ notation is very slow
> ------------------------------------------------------
>
> Key: LOG4J2-3017
> URL: https://issues.apache.org/jira/browse/LOG4J2-3017
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: Liviu Carausu
> Assignee: Volkan Yazici
> Priority: Major
> Attachments: SomeClass.groovy, TestLogging.groovy
>
>
>
> Logging of GString is very slow.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
