[
https://issues.apache.org/jira/browse/LOG4J2-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15707496#comment-15707496
]
Matt Sicker edited comment on LOG4J2-1687 at 11/30/16 4:26 AM:
---------------------------------------------------------------
{{Class.getClassLoader()}} can return null for the bootstrap {{ClassLoader}},
so that would also cause a NPE.
That is also why it would be a better idea to use {{LoaderUtil}} as it accounts
for that special case.
was (Author: jvz):
{{Class.getClassLoader()}} can return null for the bootstrap {{ClassLoader}},
so that would also cause a NPE.
> NPE in ThrowableProxy when resolving stack
> ------------------------------------------
>
> Key: LOG4J2-1687
> URL: https://issues.apache.org/jira/browse/LOG4J2-1687
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.7
> Environment: - java version "1.7.0_80" ,Java(TM) SE Runtime
> Environment (build 1.7.0_80-b15), Java HotSpot(TM) 64-Bit Server VM (build
> 24.80-b11, mixed mode)
> - Jboss EAP 5.2.0-EAP
> Reporter: Robert Christiansen
> Labels: easyfix
> Attachments: error.log, patch.diff
>
>
> NPE when logging in Java EE/OSGi environment.
> In some cases the ClassLoader (
> https://docs.oracle.com/javase/7/docs/api/java/lang/Class.html#getClassLoader()
> ) will be null for a Class.
> With the changes introduced in
> https://issues.apache.org/jira/browse/LOG4J2-1457 logging with %xEx can cause
> a NullPointerExeception when trying to resolve the stack.
> Since it's not a common occurrence in most environments I suggest the
> ThrowableProxy swallow the NPE in the same way it swallows SecurityExeception
> and other classloading exceptions to avoid extra branching for all
> environments.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
