[jboss-jira] [JBoss JIRA] (JBLOGGING-112) JBoss Logging doesn't recognize log4j implementation

[Richard Achmatowicz (JIRA)]

    [ https://issues.jboss.org/browse/JBLOGGING-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033821#comment-13033821 ] 

Richard Achmatowicz commented on JBLOGGING-112:
-----------------------------------------------

Note: when the logging implementation is chosen via org.jboss.logging.provider, if certain classes cannot be found (e.g. org.apache.log4j.LogManager), a ClassNotFoundException is raised but then swallowed and another provider is chosen. If a user specifies a specific provider but either forgets to have the provider on the classpath or chooses the wrong maven artifact, it would be nice to log the ClassNotFoundException with an appropriate warning. 

I spent a lot of time trying to use log4j and found that the problem was having an old enough maven artifact on the classpath which contained the LogManager, and the only easy way to find the problem was but debugging the sources. 

> JBoss Logging doesn't recognize log4j implementation
> ----------------------------------------------------
>
>                 Key: JBLOGGING-112
>                 URL: https://issues.jboss.org/browse/JBLOGGING-112
>             Project: JBoss Logging
>          Issue Type: Bug
>    Affects Versions: 3.2.0.Final, 3.3.0.Alpha1
>            Reporter: Richard Achmatowicz
>            Assignee: James Perkins
>             Fix For: 3.3.0.Alpha1
>
>
> There seems to be a typo in org.jboss.logging.LoggingProviders in the method tryLog4j(): the logging provider implementation used is Log4j2LoggerProvider, whereas it should be Log4jLoggerProvider.
> The net effect is that if I have log4j jars on the classpath and include a log4j configuration, the configuration gets parsed but log4j is not used as the logging provider; instead, JDK logging provider is used.
>  



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)