You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Roland Weiglhofer (JIRA)" <ji...@apache.org> on 2013/09/04 17:21:52 UTC

[jira] [Commented] (LOG4J2-377) NPE during shutdown.

    [ https://issues.apache.org/jira/browse/LOG4J2-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757863#comment-13757863 ] 

Roland Weiglhofer commented on LOG4J2-377:
------------------------------------------

Hello Ralph,
I added the NullConfiguration to my BundleActivator-class as you suggested.

  private static Configuration   logconfig = new NullConfiguration();

  @Override
  public void stop(BundleContext context) throws Exception {
    ...
    LoggerContext logcontext = (LoggerContext) LogManager.getContext();
    logcontext.updateLoggers(logconfig);
  }

I tested it and it works now. But it is just a workaround.
                
> NPE during shutdown.
> --------------------
>
>                 Key: LOG4J2-377
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-377
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0-beta9
>         Environment: OSGi R5 / R4 (Apache Felix 4.x)
>            Reporter: Roland Weiglhofer
>            Priority: Critical
>
> NPE in Log4j2-core during shutdown.
> g! Exception in thread "Thread-2" java.lang.NullPointerException
> 	at org.apache.felix.framework.BundleWiringImpl.diagnoseClassLoadError(BundleWiringImpl.java:2625)
> 	at org.apache.felix.framework.BundleWiringImpl.access$700(BundleWiringImpl.java:75)
> 	at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1967)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> 	at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:210)
> 	at org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:437)
> Exception in thread "Thread-6" java.lang.NullPointerException
> 	at org.apache.felix.framework.BundleWiringImpl.diagnoseClassLoadError(BundleWiringImpl.java:2625)
> 	at org.apache.felix.framework.BundleWiringImpl.access$700(BundleWiringImpl.java:75)
> 	at org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1967)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> 	at org.apache.logging.log4j.core.LoggerContext.stop(LoggerContext.java:210)
> 	at org.apache.logging.log4j.core.LoggerContext$ShutdownThread.run(LoggerContext.java:437)
> It's a ClassLoader-issue. I guess that log4j2-core uses the bootstrap-classloader but not the bundle-classloaer.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org