After looking at profiler data and source code it turned out that the DB access is very slow and not optimal.

      The first thing that I think is a problem is unnecessary DB access:
      35,6% - 22 274 ms com.atlassian.greenhopper.manager.rapidview.RapidViewManagerImpl.getAll
      here

      @Override
      public ServiceOutcome<List<RapidView>> getAll(final RapidViewPermissionCheck permissionCheck)
      {
      final List<RapidView> result = new ArrayList<RapidView>();
      Consumer<RapidViewAO> cacheBuilder = new Consumer<RapidViewAO>()
      {
      @Override
      public void consume(RapidViewAO rapidViewAO)
      {
      final Option<RapidView> rapidView = rapidViewCacheManager.get(rapidViewAO.getId());
      if (rapidView.isDefined() && permissionCheck.check(rapidView.get()))

      Unknown macro: { result.add(rapidView.get()); }

      }
      };
      rapidViewDao.loadAll(cacheBuilder);
      return ok(result);
      }

      we are loading all entries from rapidViewDao.loadAll(cacheBuilder)
      and then inside the cacheBuilder consumer we are doing rapidViewCacheManager.get(rapidViewAO.getId())
      which in case the record is not in cache reloads the record from DB (but we have loaded it from db a moment ago and obtained ID from it).
      Also for some reason when cache loads record from DB it does "com.atlassian.greenhopper.service.rapid.view.GenericActiveObjectsDao.load" but then "com.atlassian.greenhopper.service.rapid.view.RapidViewAOMapper.toModel" is doing access to the com.sun.proxy.$Proxy5044.isSprintsEnabled, com.sun.proxy.$Proxy5044.isSprintMarkersMigrated triggers another 2 access to the DB

      even though there are some annotations on ActiveObject that should preload the values from DB

      {qoute}

      @Table("rapidview")
      @Preload(

      {"NAME", "SAVED_FILTER_ID", "OWNER_USER_NAME", "SPRINTS_ENABLED", "SWIMLANE_STRATEGY", "CARD_COLOR_STRATEGY", "SPRINT_MARKERS_MIGRATED", "SHOW_DAYS_IN_COLUMN"}

      )
      public interface RapidViewAO extends Entity

      The other "branch" in jprofiler that takes a lot of time is execition of
      "30,4% - 19 020 ms com.atlassian.greenhopper.service.rapid.RapidViewQueryServiceImpl.getScrumBoardQueryForVisibleIssues"
      Again the problem here is with active object loading from DB in slow manner.
      The com.atlassian.greenhopper.service.rapid.view.ColumnServiceImpl.ColumnCacheLoader loads data using
      com.atlassian.greenhopper.service.rapid.view.ColumnDao#getForParent(java.lang.Long) which result in massive DB traffic:

      15,6% - 6 893 ms - 4 062 hot spot inv. SELECT "ID","STATUS_ID","POS" FROM "AO_60DB71_COLUMNSTATUS" WHERE "COLUMN_ID" = ?

      the culprit is com.atlassian.greenhopper.service.rapid.view.ColumnAO#getStatuses which performs additional access to the DB for every column in every view.
      Maybe there is some option to preload this list in AO (some sql join maybe?) to avoid additional queries to the DB

            [JSWSERVER-12239] timeout / slow "view on board" link

            G added a comment -

            Is Agile 6.6.80 also affected?

            G added a comment - Is Agile 6.6.80 also affected?

            Hi devops38,

            The issue described here is in the JIRA Agile plugin (not in JIRA) and it is fixed in the JIRA Agile plugin version 6.7.11 and above (including JIRA Software 7.0.0).

            In order to get the fix for this particular issue, you will need to upgrade to that version of the JIRA Agile plugin.

            If you need further assistance on how to perform this upgrade, please do reach out to us via a support ticket at https://support.atlassian.com

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi devops38 , The issue described here is in the JIRA Agile plugin (not in JIRA) and it is fixed in the JIRA Agile plugin version 6.7.11 and above (including JIRA Software 7.0.0). In order to get the fix for this particular issue, you will need to upgrade to that version of the JIRA Agile plugin. If you need further assistance on how to perform this upgrade, please do reach out to us via a support ticket at https://support.atlassian.com Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            DevOps COE added a comment -

            We are currently facing timeout issue in our Jira boards .
            we are using JIra 6.2.3 . IS there upgraded patch we can apply to fix this issue .

            DevOps COE added a comment - We are currently facing timeout issue in our Jira boards . we are using JIra 6.2.3 . IS there upgraded patch we can apply to fix this issue .

              ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
              dchan David Chan
              Affected customers:
              0 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: