logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LOG4J2-159) log4j.xml loading from classpath not working correct in osgi environment
Date Thu, 27 Feb 2014 22:35:25 GMT

     [ https://issues.apache.org/jira/browse/LOG4J2-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ralph Goers updated LOG4J2-159:
-------------------------------

    Fix Version/s:     (was: 2.0-rc1)
                   2.0-rc2

> log4j.xml loading from classpath not working correct in osgi environment
> ------------------------------------------------------------------------
>
>                 Key: LOG4J2-159
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-159
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: API, Core
>    Affects Versions: 2.0-beta3
>         Environment: win7, eclipse 3.7 64bit
>            Reporter: Jan Winter
>            Assignee: Ralph Goers
>            Priority: Trivial
>             Fix For: 2.0-rc2
>
>
> I have problems while loading log4j.xml configuration file in osgi environment. 
> I have the following started equinox container: 
> +--------------------------------------------------------------------------------------------------------------------------------
> | osgi> ss log4j 
> | 
> | Framework is launched. 
> | 
> | id	State Bundle 
> | 58	RESOLVED my.log4j.xml.fragment 
> | Master=136 
> | 136	RESOLVED org.apache.commons.log4j-api_2.0.0.beta3 
> | Fragments=58 
> | 137	RESOLVED org.apache.commons.log4j-core_2.0.0.beta3 
> +--------------------------------------------------------------------------------------------------------------------------------
> The log4j2 config file is packaged under my.log4j.xml.fragment.jar/log4j.xml. 
> If I have the upper bundle-configuration 
> - than the following output happens: 
> +--------------------------------------------------------------------------------------------------------------------------------
> | ERROR StatusLogger Unable to locate a logging implementation, using SimpleLogger 
> | FATAL Log4j_2 log4j-2.0.x logging 
> | ERROR Log4j_2 log4j-2.0.x logging 
> +--------------------------------------------------------------------------------------------------------------------------------
> *QUICKFIX* If I update the org.apache.commons.log4j-core_2.0.0.beta3.jar!/META-INF/MANIFEST.MF

> - append: Fragment-Host: org.apache.commons.log4j-api 
> - than log4j2 configuration is loaded and work. 
> +--------------------------------------------------------------------------------------------------------------------------------
> | osgi> ss log4j 
> |
> | Framework is launched. 
> | 
> | id	State Bundle 
> | 58	RESOLVED my.log4j.xml.fragment 
> | Master=136 
> | 136	RESOLVED org.apache.commons.log4j-api_2.0.0.beta3 
> | Fragments=58, 137 
> | 137	RESOLVED org.apache.commons.log4j-core_2.0.0.beta3 
> | Master=136 
> +--------------------------------------------------------------------------------------------------------------------------------



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
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