Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-72181

Jira logs filled with FieldLayoutItem for field named Archived errors

    XMLWordPrintable

Details

    Description

      Summary

      While navigating to the Search for issues page, the Jira log files are filled with FieldLayoutItem errors regarding null values:

      Steps to Reproduce

      1. Deploy a Jira Software 8.5+ instance
      2. Navigate to Issues > Search for issues

      Expected Results

      No error is thrown in the logs

      Actual Results

      Below exception is thrown in the atlassian.log file:

      2021-03-03 15:47:40,067-0300 http-nio-48141-exec-14 ERROR USER 947x680x1 1mngg04 0:0:0:0:0:0:0:1 /issues/ [c.a.j.issue.fields.DefaultFieldManager] FieldLayoutItem for field named Archived with ID archiveddate is null. Usually this is a transient race condition due to concurrent modification. Please contact Atlassian support if you see this log message frequently.
      2021-03-03 15:47:40,067-0300 http-nio-48141-exec-14 ERROR USER 947x680x1 1mngg04 0:0:0:0:0:0:0:1 /issues/ [c.a.j.issue.fields.DefaultFieldManager] FieldLayoutItem for field named Archiver with ID archivedby is null. Usually this is a transient race condition due to concurrent modification. Please contact Atlassian support if you see this log message frequently.
      

      Workaround

      If the custom field is linked to a specific plugin, you may try to disable and re-enable the plugin to verify if the issue stops, otherwise a cold-restart (stopping all the nodes) of the instance was reported as solving the problem on some scenarios.

      Attachments

        Issue Links

          Activity

            People

              szarazinski Sławomir Zaraziński
              7d74d3b1a350 Rodrigo Jose Zaparoli
              Votes:
              60 Vote for this issue
              Watchers:
              88 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: