[
https://issues.apache.org/jira/browse/LOG4J2-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16711985#comment-16711985
]
Stefan Küttner commented on LOG4J2-1570:
----------------------------------------
If one starts using functional syntax this issue becomes more serious as more
and more log entries are not attributable to the logging class/line number,
making logs less useful for diagnostics.
> Logging with a lambda expression with a method call that also logs causes
> logs within method call to reference line num and method name as parent method
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-1570
> URL: https://issues.apache.org/jira/browse/LOG4J2-1570
> Project: Log4j 2
> Issue Type: Bug
> Components: API
> Affects Versions: 2.6.2
> Reporter: Joel Berta
> Priority: Minor
> Labels: easyfix, newbie
>
> While logging a message using lambda expressions. If i call a method within
> the log message (i.e logger.info(() -> "foo" +bar()) which also logs
> messages, those logs within the called method will reference the line number
> and method name of the method which invoked it.
> Running the following code demonstrates this issue:
> {code:title=TestingLogging.java|borderStyle=solid}
> private static final Logger LOGGER =
> LogManager.getLogger(TestingLogging.class);
> public static String foo(){
> LOGGER.info("bar");
> return "foo";
> }
> public static void main(String[] args){
> System.out.println("correct method reference: ");
> LOGGER.info(foo());
> System.out.println("\nincorrect method reference: ");
> // causes logging in foo to reference
> // this line number and method (main)
> LOGGER.info(() -> foo());
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
