[
https://issues.apache.org/jira/browse/LOG4J2-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137272#comment-14137272
]
Anton Korenkov commented on LOG4J2-835:
---------------------------------------
I'll try explain on next example. I have next pattern:
{noformat}
pattern="[%d] [%t] %-5p %c %x - %m%n"
{noformat}
Wigh log4j 1.2.17 I'll see next stack trace in case of exception:
{noformat}
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
{noformat}
But with logj4 2.0.2:
{noformat}
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[?:1.7.0_17]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[?:1.7.0_17]
at java.lang.Thread.run(Thread.java:722) [?:1.7.0_17]
{noformat}
As you may see there is one difference at the end of the line: [?:1.7.0_17]
That what I meant by lib name and version.
> Possibility to turn off logging of lib name and version in exception stack
> trace
> --------------------------------------------------------------------------------
>
> Key: LOG4J2-835
> URL: https://issues.apache.org/jira/browse/LOG4J2-835
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0.2
> Reporter: Anton Korenkov
> Priority: Minor
>
> New feature in log4j-2 is library name and version appending while logging
> stack trace. Sometimes it's helpful, but in some cases it will be good to
> turn off this feature by setting new property (e.g. "appned-lib") to false
> for example.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
