logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neale Upstone (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-293) classloader URI scheme broken or insufficient when using Log4jContextListener
Date Sat, 31 Aug 2013 22:20:51 GMT

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

Neale Upstone commented on LOG4J2-293:
--------------------------------------

It looks like this patch fixes only the NPE, but not the reconfiguration issue, as Ralph had
alluded to.

That still remains a gotcha as Log4j2 should not silently ignore configuration as it does.

                
> classloader URI scheme broken or insufficient when using Log4jContextListener
> -----------------------------------------------------------------------------
>
>                 Key: LOG4J2-293
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-293
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Configurators
>    Affects Versions: 2.0-beta7
>            Reporter: Neale Upstone
>            Assignee: Nick Williams
>              Labels: documentation
>             Fix For: 2.0-beta9
>
>         Attachments: ConfigurationFactory.java, LOG4J2-293.patch, TestConfigurator.java
>
>
> I'm trying to migrate to Log4j2, and things looked promising when I spotted Log4jContextListener.
> However, there are too many holes.
> Firstly, I tried using classpath: as a scheme, and nothing blew up, so I assumed I'd
got it right.
> Then I *looked at the code* (which shouldn't be how we find out) and eventually discovered
some code relating to a 'classloader' scheme.
> Still silent failure.  It seems that the classpath is not being searched, perhaps just
the WAR classloader, not the JARs in WEB-INF/lib.
> Next I tried omitting the / (i.e. using classloader:log4j2.xml) and got a NullPointerException.
> Can you please document what schemes are supported and what you expect them to do, and
*not fail silently* when a configuration file is specified, but nothing happens.

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


Mime
View raw message