After upgrade to ATST plugin version 2.18.0 or 3.11.0 Jira is encountering performance issues along with OOM exceptions causing the application to crash

XMLWordPrintable

    • 10.03
    • 10
    • Severity 1 - Critical
    • 13
    • Hide

      We released two new versions of ATST that fix the issue: 2.19.0+ and 3.12.0+. They are publicly available on the marketplace for customers to update.

      Show
      We released two new versions of ATST that fix the issue:  2.19.0+  and  3.12.0+ . They are publicly available on the marketplace for customers to update.

      Issue Summary

      This issue was cloned from the Confluence bug as this is also impacting Jira.

      After upgrade to ATST plugin version 2.18.0 or 3.11.0 Jira is encountering performance issues along with OOM exceptions causing the application to crash

      Jira 10.3.21 has ATST 2.18.0 bundled.
      Jira 11.3.6 has ATST 3.11.0 bundled.

      Steps to Reproduce

      1. Install Jira version 10.3.21 or Jira 11.3.6
      2. Wait for the DCDP diagnostics transfer job to run

      Expected Results

      • DCDP diagnostics transfer job runs without issues

      Actual Results

      DCDP diagnostics transfer job failing with OOM exceptions

      2026-04-28 04:14:06,208 ERROR [Caesium-1-2] [scheduler.caesium.impl.SchedulerQueueWorker] executeJob Unhandled exception thrown by job QueuedJob[jobId=DcdpTransferJob,deadline=1777339636941]
      java.lang.OutOfMemoryError: Java heap space 

      Workaround

      Apply one of the following workarounds:

      Workaround 1: Upgrade to a fixed version of the "Atlassian Troubleshooting and Support Tools" app:

      1. Visit Jira Admin -> Manage Apps, and update to a fixed version of the app:
        • For Jira 11: 3.12.0 or above
        • For Jira 10: 2.19.1 or above

      Workaround 2: Disable just the DCDP security metric collection via a dark feature:

      1. Log in as a Jira admin.
      2. Go to: <baseURL>/secure/admin/SiteDarkFeatures!default.jspa
      3. In Enable dark feature, add:
        com.atlassian.troubleshooting.dcdp.security.metric.collection.disabled 
      4. Confirm it appears in the list of enabled dark features.

      Workaround 3: Disable just the DCDP security metric collection via a system property:

      1. Add the following System Property to each node:
        -Datlassian.darkfeature.com.atlassian.troubleshooting.dcdp.security.metric.collection.enabled=false 
      2. Rolling restart each Jira node

              Assignee:
              Murillo Ichikawa
              Reporter:
              Allan O'Rourke
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: