[
https://issues.apache.org/jira/browse/LOG4J2-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924922#comment-15924922
]
Ralph Goers edited comment on LOG4J2-1359 at 3/14/17 8:27 PM:
--------------------------------------------------------------
It would be a direct replacement for the method in ReflectionUtil and
calcLocation in Log4jLogEvent.
The MDCFilter benchmark shows that a logging operation that rejects the event
based on something in the MDC takes about 50 ns. With stackWalkerGetImmediate
taking over 1 ms it would be an intolerable performance hit to add it in
AbstractLogger. At roughly 2 ms though, this isn't much of an impact if you
are logging to a file or a socket.
was (Author: [email protected]):
It would be a direct replacement for the method in ReflectionUtil and
calcLocation in Log4jLogEvent.
> Add support for Java 9 StackWalker API in ReflectionUtil
> --------------------------------------------------------
>
> Key: LOG4J2-1359
> URL: https://issues.apache.org/jira/browse/LOG4J2-1359
> Project: Log4j 2
> Issue Type: Improvement
> Components: API
> Environment: Java 1.9+
> Reporter: Matt Sicker
> Assignee: Ralph Goers
> Labels: jdk9
>
> [StackWalker|http://download.java.net/jdk9/docs/api/java/lang/StackWalker.html]
> Based on the functional nature of this API, supporting it may require
> compiling at least one class using javac 1.9 and reflectively loading it in
> ReflectionUtil similar to how Spring supports newer JDK APIs.
> Without support for StackWalker, ReflectionUtil will fall back to using a
> slower API in Java 1.9. This is because the Reflection class is a
> sun-internal class which are no longer exported to non-JDK code without
> setting special command line flags.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
