logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Roland Weiglhofer (JIRA)" <j...@apache.org>
Subject [jira] [Created] (LOG4J2-373) Classloader issue in OSGi-environment
Date Tue, 27 Aug 2013 07:19:53 GMT
Roland Weiglhofer created LOG4J2-373:

             Summary: Classloader issue in OSGi-environment
                 Key: LOG4J2-373
                 URL: https://issues.apache.org/jira/browse/LOG4J2-373
             Project: Log4j 2
          Issue Type: Bug
          Components: API, Core
    Affects Versions: 2.0-beta9
         Environment: OSGi R5 / R4 (Apache Felix 4.x)
            Reporter: Roland Weiglhofer
            Priority: Critical

Using Log4j2 in a bundle causes following error:
ERROR StatusLogger org.apache.logging.log4j.core.impl.Log4jContextFactory does not implement
ERROR StatusLogger Unable to locate a logging implementation, using SimpleLogger

printing the ClassLoaders in LogManager gives me following output:

org.apache.logging.log4j.spi.LoggerContextFactory loaded by org.apache.logging.log4j-api [13]
org.apache.logging.log4j.core.impl.Log4jContextFactory loaded by sun.misc.Launcher$AppClassLoader@35a16869

We have two different ClassLoaders. That's why the implementation is not assignable. The core
uses the bootstrap-classloader and the api uses the bundle-classloader.

Workaround needed. Thx

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

View raw message