Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-34138

log4j:WARN Please initialize the log4j system properly.

      NOTE: This bug report is for Confluence Cloud. Using Confluence Server? See the corresponding bug report.

      Even though Confluence is properly running after the installation/migration/upgrade, the following message is displayed in the catalina.out logs:

      log4j:WARN No appenders could be found for logger (com.atlassian.confluence.extra.webdav.DefaultConfluenceDavSessionStore).
      log4j:WARN Please initialize the log4j system properly.
      

      It appears that the default log4j configuration doesn't have the proper appender files set up for example:

      • com.atlassian.confluence.extra.webdav.DefaultConfluenceDavSessionStore
      • com.amazonaws.internal.config.InternalConfig
      • org.apache.commons.httpclient.params.DefaultHttpParams

          Form Name

            [CONFCLOUD-34138] log4j:WARN Please initialize the log4j system properly.

            Not valid for cloud.

            jonah (Inactive) added a comment - Not valid for cloud.

            Same here.

            Tim Robertson added a comment - Same here.

            We also facing the same issue.

            However, I replaced "WARN >> DEBUG" and it shows lots of logs...

            Kindly, at least confirm if this will not create any issue/ problem later in production.

            Chetan Patil added a comment - We also facing the same issue. However, I replaced "WARN >> DEBUG" and it shows lots of logs... Kindly, at least confirm if this will not create any issue/ problem later in production.

            Neil Tai added a comment -

            we have same problem, any updates on this?

            Neil Tai added a comment - we have same problem, any updates on this?

            Mike added a comment -

            I'm seeing the same thing in Jira 6.4.8. Any advice on how to fix it?

            Mike added a comment - I'm seeing the same thing in Jira 6.4.8. Any advice on how to fix it?

            Shai Dahan added a comment -

            Same issue on the current Confluence latest version 5.8.8

            log4j:WARN No appenders could be found for logger (com.atlassian.plugin.spring.scanner.util.ProductFilterUtil).
            log4j:WARN Please initialize the log4j system properly.
            log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

            Shai Dahan added a comment - Same issue on the current Confluence latest version 5.8.8 log4j:WARN No appenders could be found for logger (com.atlassian.plugin.spring.scanner.util.ProductFilterUtil). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

            We have the same issue. where found this file?

            Olga Plisko added a comment - We have the same issue. where found this file?

            Hmm, where exactly should i put this file and where from do i get it? I have the same problem (getting the same message in log), eventually i can access the first few windows, but then get error 500 - page

            Raphael Reber added a comment - Hmm, where exactly should i put this file and where from do i get it? I have the same problem (getting the same message in log), eventually i can access the first few windows, but then get error 500 - page

            you need a log4j.properties file under src to initialize.

            Best wishes

            Ningning Ma added a comment - you need a log4j.properties file under src to initialize. Best wishes

            Sam Kerr added a comment -

            I also have this issue. Is there anything to do and fix it? It is somewhat annoying to get the "Open a Support Ticket" answer, since it appears to happen to several people.

            Sam Kerr added a comment - I also have this issue. Is there anything to do and fix it? It is somewhat annoying to get the "Open a Support Ticket" answer, since it appears to happen to several people.

            Issue still occuring with Confluence v5.5.6:

            INFO: Starting service Tomcat-Standalone
            Aug 23, 2014 4:41:23 PM org.apache.catalina.core.StandardEngine startInternal
            INFO: Starting Servlet Engine: Apache Tomcat/7.0.47
            2014-08-23 16:41:46,741 INFO [localhost-startStop-1] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 5.5.6 [build 5527 based on commit hash d6c318572c182872608bdc1754f542eab16839cb]
            SLF4J: Class path contains multiple SLF4J bindings.
            SLF4J: Found binding in [jar:file:/usr/local/confluence-5.0.3/confluence/WEB-INF/lib/slf4j-log4j12-1.6.4.jar!/org/slf4j/impl/StaticLoggerBinder.class]
            SLF4J: Found binding in [bundle://29.0:1/org/slf4j/impl/StaticLoggerBinder.class]
            SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
            log4j:WARN No appenders could be found for logger (org.apache.http.impl.conn.PoolingClientConnectionManager).
            log4j:WARN Please initialize the log4j system properly.
            log4j:WARN No appenders could be found for logger (com.atlassian.confluence.extra.webdav.DefaultConfluenceDavSessionStore).
            log4j:WARN Please initialize the log4j system properly.
            

            Note also the entry referencing "Class path contains multiple SLF4J bindings". Cause and effect?

            Mark Symons added a comment - Issue still occuring with Confluence v5.5.6: INFO: Starting service Tomcat-Standalone Aug 23, 2014 4:41:23 PM org.apache.catalina.core.StandardEngine startInternal INFO: Starting Servlet Engine: Apache Tomcat/7.0.47 2014-08-23 16:41:46,741 INFO [localhost-startStop-1] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 5.5.6 [build 5527 based on commit hash d6c318572c182872608bdc1754f542eab16839cb] SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/usr/local/confluence-5.0.3/confluence/WEB-INF/lib/slf4j-log4j12-1.6.4.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [bundle://29.0:1/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. log4j:WARN No appenders could be found for logger (org.apache.http.impl.conn.PoolingClientConnectionManager). log4j:WARN Please initialize the log4j system properly. log4j:WARN No appenders could be found for logger (com.atlassian.confluence.extra.webdav.DefaultConfluenceDavSessionStore). log4j:WARN Please initialize the log4j system properly. Note also the entry referencing "Class path contains multiple SLF4J bindings". Cause and effect?

            Hi yehonatan.devorkin

            Thanks for getting in touch. The problem you describe sounds like something that our support team would be able to help you with. Could I ask that you create a support request on https://support.atlassian.com.

            Regards
            Steve Haffenden
            Confluence Bugmaster
            Atlassian

            Steve Haffenden (Inactive) added a comment - Hi yehonatan.devorkin Thanks for getting in touch. The problem you describe sounds like something that our support team would be able to help you with. Could I ask that you create a support request on https://support.atlassian.com . Regards Steve Haffenden Confluence Bugmaster Atlassian

            I've upgraded today our test environment from Confluence 5.5.3 to 5.5.6 and cannot access Confluence GUI anymore.
            The logs hangs on the same output has appear here.

            Any update about it from Atlassian end?

            Thanks in advance.

            Yehonatan Devorkin added a comment - I've upgraded today our test environment from Confluence 5.5.3 to 5.5.6 and cannot access Confluence GUI anymore. The logs hangs on the same output has appear here. Any update about it from Atlassian end? Thanks in advance.

            Any updates on this? We too have a similar message while the Confluence is being restarted.

            Regards,
            Rahul

            Rahul Savaikar added a comment - Any updates on this? We too have a similar message while the Confluence is being restarted. Regards, Rahul

            Thanks for raising this issue, Giuliano!

            If the message has any meaning, I'd like to fix the log4j initialization process accordingly – please tell us how! Otherwise, I'd rather not have the WARN message...

            Normand Brousseau added a comment - Thanks for raising this issue, Giuliano! If the message has any meaning, I'd like to fix the log4j initialization process accordingly – please tell us how! Otherwise, I'd rather not have the WARN message...

              Unassigned Unassigned
              gdecampos Giuliano C.
              Affected customers:
              16 This affects my team
              Watchers:
              37 Start watching this issue

                Created:
                Updated:
                Resolved: