[logback-dev] [JIRA] Commented: (LBCLASSIC-159) Invalid multiple configuration file warning

Derek Mahar (JIRA) noreply-jira at qos.ch
Thu Aug 5 03:10:18 CEST 2010


    [ http://jira.qos.ch/browse/LBCLASSIC-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11811#action_11811 ] 

Derek Mahar commented on LBCLASSIC-159:
---------------------------------------

I have implemented a fix for LBCLASSIC-159 (see http://github.com/derekmahar/logback/commit/1990e7c9c0e35ba408f73a2c654e8d292a0849af) that essentially does what Robert Elliot recommends in http://marc.info/?l=logback-user&m=128094084217480&w=2 and uses a set instead of a list to hold the resources that the classloader returns, effectively eliminating any duplicate classpath resources. I have successfully tested the fix with Logback 0.9.24, SLF4J 1.6.1, and WebLogic 10.3.2.  With this fix in place, Logback no longer displays the duplicate classpath entry status messages (or any of the other informational messages) to standard output.

> Invalid multiple configuration file warning
> -------------------------------------------
>
>                 Key: LBCLASSIC-159
>                 URL: http://jira.qos.ch/browse/LBCLASSIC-159
>             Project: logback-classic
>          Issue Type: Bug
>          Components: Other
>    Affects Versions: 0.917
>         Environment: Resin webapp
>            Reporter: Hontvári József
>            Assignee: Logback dev list
>
> I receive strange warnings in the status info. It says that logback.xml, which in this case comes from a file and not from the classpath, occurs multiple times. The file is specifies and logged using absolute path, so even relative paths cannot cause the warning.
> Logback configuration file is specified by the system property "logback.configurationFile". It is done by the Resin application server, somehow it is able to supply different properties for different web applications. I don't think this is important, however. Maybe I am doing something wrong, but at least the message doesn't help.  
> 20:36:34,236 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [file:/C:/Progra~1/mireka/conf/logback.xml] at [file:/C:/Progra~1/mireka/conf/logback.xml]  
> 20:36:34,236 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:/C:/Progra~1/mireka/conf/logback.xml] occurs multiple times on the classpath.               
> 20:36:34,236 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:/C:/Progra~1/mireka/conf/logback.xml] occurs at [file:/C:/Progra~1/mireka/conf/logback.xml] 
> 20:36:34,236 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:/C:/Progra~1/mireka/conf/logback.xml] occurs at [file:/C:/Progra~1/mireka/conf/logback.xml] 
> 20:36:34,236 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [file:/C:/Progra~1/mireka/conf/logback.xml] occurs at [file:/C:/Progra~1/mireka/conf/logback.xml] 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       


More information about the logback-dev mailing list