As an Admin, I would not like to see warning messages in the logs for DefaultIndexEngine if it should not be a concern to the admins

XMLWordPrintable

    • 2
    • 10

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Problem Definition

      Currently we see the following warnings in the logs:

      /rest/greenhopper/1.0/xboard/work/allData.json [atlassian.jira.index.DefaultIndexEngine] Tried to reopen the IndexReader, but it threw AlreadyClosedException. Opening a fresh IndexReader.
      
      
      
       /rest/jpo/1.0/issuelinks/commit [atlassian.jira.index.DefaultIndexEngine] Tried to reopen the IndexReader, but it threw AlreadyClosedException. Opening a fresh IndexReader.
      
      
      

      This happens because of the way JIRA provides access to its Lucene index to portfolio/agile. This shouldn't have any negative effects whatsoever. However, this is logged as a warning and would cause problems to JIRA admins trying to figure out if they should perform any corrective measure.

      Suggested Solution  

      • Change the log entry from WARN to INFO or any other appropriate categorization
        or
      • remove the entry to the log entirely.

      Workaround 

      You may filter out these entries from the logs as follows:

      1. Shut down JIRA
      2. Add the following lines to the log4j.properties file:
        log4j.logger.com.atlassian.jira.index.DefaultIndexEngine = ERROR, console, filelog
        log4j.additivity.com.atlassian.jira.index.DefaultIndexEngine = false
        
      3. Start JIRA again

      This should help resolve your issue and reduce the amount of warning messages in your logs generated from this particular class.

            Assignee:
            Unassigned
            Reporter:
            Mohamed Riza (Inactive)
            Votes:
            9 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: