Uploaded image for project: 'logback'
  1. logback
  2. LOGBACK-470

Strange new error message during application startup with 0.9.28

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 0.9.28
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      Description

      An error message like this is emitted upon startup of an application that contains the logback.xml in one of its jars:
      15:36:20,346 |-ERROR in ch.qos.logback.core.joran.spi.ConfigurationWatchList@47ad6b4b - URL [jar:file:/path/to.jar!/logback.xml] is not of type file

      This started with Logback 0.9.28 and I guess (!!) it's a side-effect of the LBCLASSIC-245 fix...
      The logback.xml file in question does not have scan activated, btw.

        Activity

        Hide
        noreply.ceki@qos.ch Ceki Gulcu added a comment -
        Show
        noreply.ceki@qos.ch Ceki Gulcu added a comment - Fixed in http://github.com/ceki/logback/commit/8be92873
        Hide
        mfranz@intershop.de Michael Franz added a comment -

        After applying this fix I get warnings for all included files (scanning is deactivated):
        ch.qos.logback.core.joran.util.ConfigurationWatchListUtil@21c4fd92: Null ConfigurationWatchList. Cannot add file:/D:/dev/.../logback-lilith.xml

        Show
        mfranz@intershop.de Michael Franz added a comment - After applying this fix I get warnings for all included files (scanning is deactivated): ch.qos.logback.core.joran.util.ConfigurationWatchListUtil@21c4fd92: Null ConfigurationWatchList. Cannot add file:/D:/dev/.../logback-lilith.xml
        Hide
        noreply.ceki@qos.ch Ceki Gulcu added a comment - - edited

        The patch changes the level of the status message from ERROR to INFO. I don't see how that can change the ConfigurationWatchList reference in logger context to null. Something else is going on.

        Show
        noreply.ceki@qos.ch Ceki Gulcu added a comment - - edited The patch changes the level of the status message from ERROR to INFO. I don't see how that can change the ConfigurationWatchList reference in logger context to null. Something else is going on.
        Hide
        mfranz@intershop.de Michael Franz added a comment -

        You are right I have re-testet it. The warning already came without this fix. I'll file a new bug entry.

        Show
        mfranz@intershop.de Michael Franz added a comment - You are right I have re-testet it. The warning already came without this fix. I'll file a new bug entry.
        Hide
        ejain Eric Jain added a comment -

        ERROR or not, should this message appear at all with <configuration scan="false">?

        Show
        ejain Eric Jain added a comment - ERROR or not, should this message appear at all with <configuration scan="false">?

          People

          • Assignee:
            noreply.ceki@qos.ch Ceki Gulcu
            Reporter:
            jhuxhorn Joern Huxhorn
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: