Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-16414

Remove errorLog from JIRA's log4j.properties

    XMLWordPrintable

Details

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      The errorLog in JIRA is configured for an old appender (from atlassian-core) that JIRA and no one else ever looks at. Worse it has been seen to throw NullPointerExceptions:

      java.lang.NullPointerException 
        at com.atlassian.core.logging.ThreadLocalErrorCollection.isEnabled(ThreadLocalErrorCollection.java:70) 
        at com.atlassian.core.logging.ThreadLocalErrorCollection.add(ThreadLocalErrorCollection.java:30) 
        at com.atlassian.core.logging.ThreadLocalErrorLogAppender.append(ThreadLocalErrorLogAppender.java:20) 
        at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:221) 
        at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:57) 
        at org.apache.log4j.Category.callAppenders(Category.java:187) 
        at org.apache.log4j.Category.forcedLog(Category.java:372)
        ...

      including this one.

      The solution is to remove the errorLog from the {rootLogger}} property like so:

      log4j.rootLogger=WARN, console, filelog

      This will be done by default as part of JIRA 4.

      Attachments

        Activity

          People

            jed Jed Wesley-Smith (Inactive)
            jed Jed Wesley-Smith (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: