[
https://issues.apache.org/jira/browse/LOG4J2-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109726#comment-14109726
]
Edwin F. López commented on LOG4J2-784:
---------------------------------------
Hi and thanks.
I've stumbled upon this problem too and the configuration correction fixed it
as expected. However, I was thinking that the default behavior should be to
includeLocation="true" due to the "least expected surprise" factor. I
understand that for performance reasons this options is disabled by default,
but I also believe that the behaviour should be consistent. Don't you agree?
Just commenting....
Thanks again.
> AsyncLoggers and PatternLayout with class/method/line
> -----------------------------------------------------
>
> Key: LOG4J2-784
> URL: https://issues.apache.org/jira/browse/LOG4J2-784
> Project: Log4j 2
> Issue Type: Bug
> Components: Layouts
> Affects Versions: 2.0.1
> Environment: OSX/Win7 64b, Java7/8, Eclipse/IDEA
> Reporter: Martin Vehovský
>
> Using slf4j binding.
> VM options:
> {{-DLog4jContextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector}}
> Appender:
> {code}
> <Console name="Console" target="SYSTEM_OUT">
> <PatternLayout pattern="%highlight{%p | %d{DEFAULT} | %t | %C{1}.%M(%L)
> | %m%n}{STYLE=Logback}"/>
> </Console>
> {code}
> Log message:
> DEBUG | 2014-08-18 19:05:13,795 | main | ?.() | HashSet: [A, B]
> Log message without the VM option "Log4jContextSelector":
> DEBUG | 2014-08-18 19:09:43,608 | main | Main.main(32) | HashSet: [A, B]
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
