Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-29200

Handle 'Method getHtml threw exception for reference $column in template templates/jira/issue/table/issuetable-issue.vm' errors more gracefully

    XMLWordPrintable

Details

    Description

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

      This error message appears often, in JIRA logs:

      Method getHtml threw exception for reference $column in template templates/jira/issue/table/issuetable-issue.vm

      This message is a symptom, not a root cause, from what I can tell. Here's what I found:

      1. I think this is the best description of it:

        If my search result contiains and issue for which myField is null/empty, then I get an error in the Jira search, as well as an exception in my Jira log. If modify my entry to have a non-Null/blank field in myField, then the Entry Navigator works as expected, with no errors returned.

      2. Looking through SAC tickets (note: these are not public), we have what would appear to be 45 different root causes, including NPEs, Illegal Argument exceptions, GreenHopper Rank exceptions, even OutOfMemory Errors. They apply to all different custom field types.

      Improvement Request
      In general I'm thinking this is an innocuous error, given that the true root cause is what error message appears below it (the NPE or otherwise), but perhaps it's worth implementing better error handling to indicate which custom field has the problem, and for which issue ID. This error is spamming the logs and is quite common.

      Workaround
      If you're a customer and are seeing this issue in your environment, look at the stacktrace error below this one to identify a true root cause.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              jlargman Jeremy Largman
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: