[
https://issues.apache.org/jira/browse/LOG4J2-832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137352#comment-14137352
]
Gary Gregory edited comment on LOG4J2-832 at 9/17/14 3:40 PM:
--------------------------------------------------------------
I am using:
{noformat}
java version "1.7.0_67"
Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
{noformat}
and:
{noformat}
Apache Maven 3.2.3 (33f8c3e1027c3ddde99d3cdebad2656a31e8fdf4;
2014-08-11T16:58:10-04:00)
Maven home: C:\Java\apache-maven-3.2.3
Java version: 1.7.0_67, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_67\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
{noformat}
was (Author: garydgregory):
I am using:
{noformat}
java version "1.7.0_67"
Java(TM) SE Runtime Environment (build 1.7.0_67-b01)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
{noformat}
> ThrowableProxy fails if sun.reflect.misc.Trampoline is in logged stack trace
> ----------------------------------------------------------------------------
>
> Key: LOG4J2-832
> URL: https://issues.apache.org/jira/browse/LOG4J2-832
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0, 2.0.2
> Environment: Java 1.7u60, Java 1.7u25
> Reporter: Seth Leger
> Priority: Blocker
> Attachments: LOG4J2-832.patch, Log4j2MethodUtilTrampolineTest.java,
> Log4j2MethodUtilTrampolineTest.java, ggregory-log4j2.patch, pom.xml
>
>
> When the Logger attempts to log a message with an exception stack trace, it
> uses the ThrowableProxy class to introspect classes in the stack trace frames.
> If the class sun.reflect.misc.Trampoline is in the stack trace, the
> introspection performed by ThrowableProxy will fail causing a java.lang.Error
> to be thrown by the Logger call.
> The sun.reflect.misc.Trampoline class is used by the
> sun.reflect.misc.MethodUtil class to perform reflection-based method
> invocations. MethodUtil is widely used by libraries to perform method
> invocations. I've encountered this problem when invoking methods over JMX and
> inside Jetty.
> I am classifying this as a blocker because it means that any logging
> statement that is logging a Throwable message containing a MethodUtil-based
> reflection stack trace can cause a java.lang.Error to be thrown by Log4j2.
> I will attach a unit test for this failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
