logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Sicker (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1467) [OSGi] Missing import package
Date Wed, 27 Jul 2016 00:30:20 GMT

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

Matt Sicker commented on LOG4J2-1467:
-------------------------------------

It would also be nice to have a unit or integration test for this, especially if a less hacky
method can be supported in the future.

> [OSGi] Missing import package
> -----------------------------
>
>                 Key: LOG4J2-1467
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1467
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 2.6.2
>         Environment: Enterprise OSGi application
>            Reporter: Ralf
>             Fix For: 2.7
>
>
> The Import-Package statement in log4j-api-2.6.2.jar is missing the package "org.apache.logging.log4j.core.lookup".
This results in the following log output while starting a enterprise OSGi application:
> Blueprint Extender: 3 WARN JNDI lookup class is not available because this JRE does not
support JNDI. JNDI string lookups will not be available, continuing configuration. java.lang.ClassNotFoundException:
org.apache.logging.log4j.core.lookup.JndiLookup
>         at java.lang.Class.forName(Class.java:256)
>         at org.apache.logging.log4j.util.LoaderUtil.loadClass(LoaderUtil.java:122)
>         at org.apache.logging.log4j.util.LoaderUtil.newInstanceOf(LoaderUtil.java:141)
>         at org.apache.logging.log4j.util.LoaderUtil.newCheckedInstanceOf(LoaderUtil.java:168)
>         at org.apache.logging.log4j.core.util.Loader.newCheckedInstanceOf(Loader.java:301)
>         at org.apache.logging.log4j.core.lookup.Interpolator.<init>(Interpolator.java:95)
>         at org.apache.logging.log4j.core.config.AbstractConfiguration.<init>(AbstractConfiguration.java:116)
> and
> Blueprint Extender: 3 WARN JMX runtime input lookup class is not available because this
JRE does not support JMX. JMX lookups will not be available, continuing configuration. java.lang.ClassNotFoundException:
org.apache.logging.log4j.core.lookup.JmxRuntimeInputArgumentsLookup
>    (Stacktrace like above)
> As local fix I added 'DynamicImport-Package: *' to the MANIFEST.MF. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message