Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-2687

JIRA is blocked by burndown chart calculating (wrong BURNDOWN_START_DATE setting)

    XMLWordPrintable

Details

    • Bug
    • Resolution: Not a bug
    • Highest
    • GreenHopper, 5.4
    • 5.2 (JIRA 4.1 Compatible)
    • None
    • JIRA 4.1.2 + GH 5.2

    Description

      Symptom

      When accessing burndown chart for a specific version, JIRA instnace is blocked and CPU usage is maxing out.

      Cause

      Through thread dumps, I found that thread never jumped out of the below loop in com.pyxis.greenhopper.charts.GHChartUtil numberOfWorkingDays() function.

      while (end.after(begin))
              {
                  begin.add(GregorianCalendar.DAY_OF_YEAR, 1);
                  int day = begin.get(GregorianCalendar.DAY_OF_WEEK);
                  if (day > minBound && day < maxBound && !nonWorkingDates.contains(begin.getTime()))
                  {
                      days++;
                  }
              }
      

      Then go to the database, found that in GreenHopper project configuration, the version has a wrong start date setting as below

        <entry>
          <string>BURNDOWN_START_DATE_10475</string>
          <long>-61826266800000</long>
        </entry>
      

      Workaround

      Reset version start date in Planning Board may resolve the problem.

      So far I can't find the reason that may cause BURNDOWN_START_DATE being set as a negative value.

      Attachments

        Activity

          People

            jchuet JC
            kren Kelson Ren
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: