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

Slow /rest/ical/1.0/ical/config/query/options times out for Team Calendar

XMLWordPrintable

    • 7.06
    • 88
    • Severity 2 - Major
    • 216
    • Hide
      Atlassian Update – 21 March 2025

      Dear Customers,

      We appreciate your effort in reporting and providing feedback regarding this issue. We are excited to inform you that the bug has been addressed in the forthcoming Confluence DC 9.4.0 version.

      This fix has been implemented in the Confluence DC and is fully compatible with all supported Jira versions. As a result, we have created a ticket CONFSERVER-99485 within the Confluence Data Center project that correctly tracks the fixed version and effectively resolves this issue.

      At the same time, please be aware that the “Saved filter” query option still depends on the endpoint referenced in this bug, which may render only this option unusable in larger Jira instances. The workaround is presented in the UI - the JQL query option offers a way to search by the filter keyword, which results in exactly the same result. Furthermore, we have initiated JSWSERVER-26345 to monitor this issue, specifically focusing on the affected query option.

      Best regards,

      Krystian M
      Software Engineer, Jira DC

      Show
      Atlassian Update – 21 March 2025 Dear Customers, We appreciate your effort in reporting and providing feedback regarding this issue. We are excited to inform you that the bug has been addressed in the forthcoming Confluence DC 9.4.0 version. This fix has been implemented in the Confluence DC and is fully compatible with all supported Jira versions. As a result, we have created a ticket  CONFSERVER-99485 within the Confluence Data Center project that correctly tracks the fixed version and effectively resolves this issue. At the same time, please be aware that the “ Saved filter ” query option still depends on the endpoint referenced in this bug, which may render only this option unusable in larger Jira instances. The workaround is presented in the UI - the JQL query option offers a way to search by the filter keyword, which results in exactly the same result. Furthermore, we have initiated JSWSERVER-26345 to monitor this issue, specifically focusing on the affected query option. Best regards, Krystian M Software Engineer, Jira DC

      Issue Summary

      REST API request /rest/ical/1.0/ical/config/query/options is taking a long time to return the full set of data that cause the JIRA event creation on Confluence team calendar fails with the timeout error.

      Environment

      Large Jira instance with

      • 2000+ projects, or
      • 30000+ search filters

      Steps to Reproduce

      1. Configure 2000 projects and 30,000 filters in Jira
      2. Go to Confluence, create a Calendar event that pulls in Jira projects

      Expected Results

      Correctly allow the user to choose the Jira project and proceed without error.

      Actual Results

      The below exception is thrown in the atlassian-confluence.log file:

      2019-07-24 04:37:44,960 ERROR [http-nio-8080-exec-1] [calendar3.rest.ExceptionMappers.GeneralExceptionMapper] getResponseError General exception happen on calendar resources
 -- referer: https://confluence/display/ZTEST/calendar/xxxxxxx-9b64-44c5-8a93-810942e14566?calendarName=Release%20Calendar | url: /rest/calendar-services/1.0/calendar/jira/xxxxxxx-cefa-3cdd-9508-4a4945627d9a/query/options.json | userName: admin
com.atlassian.sal.api.net.ResponseException: java.net.SocketTimeoutException: Read timed out

      access_log of Jira show:

      10.0.0.111 252x3288526x4 admin [15/Aug/2019:04:17:18 +0000] http-nio-8080-exec-1 admin "GET /rest/ical/1.0/ical/config/query/options?_=1111111111&xoauth_requestor_id=admin HTTP/1.1" 200 511689 293768 "-" "Apache-HttpClient/4.5.5 (Java/1.8.0)" "xxxxx"

      293768 = 4 minutes 54 seconds

      Notes

      /rest/ical/1.0/ical/config/query/options contains the following data

      • List of projects
      • List of Search filters
      • Names of viewable fields

      Workaround

      Increase the timeout for the calendar connection as mentioned in the KB article JIRA Calendar Read Timed Out.

            [JSWSERVER-16764] Slow /rest/ical/1.0/ical/config/query/options times out for Team Calendar

            Jean Orengo made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 1008170 ]
            Krystian M made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]

            Krystian M added a comment -

            A fix for this issue is available in Confluence Data Center 9.4.0 - link to upgrade.

            Krystian M added a comment - A fix for this issue is available in Confluence Data Center 9.4.0 - link to upgrade .
            SET Analytics Bot made changes -
            UIS Original: 215 New: 216
            SET Analytics Bot made changes -
            UIS Original: 212 New: 215
            Krystian M made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 1002063 ]
            SET Analytics Bot made changes -
            UIS Original: 214 New: 212
            Krystian M made changes -
            Current Status Original: {panel:title=Atlassian Update – 21 March 2025|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff}
            Dear Customers,

            Thank you for taking the time to file and comment on this issue.

            We're aware that this issue is having an impact on the workflows of multiple customers and we're looking to provide a fix shortly after the release of the Jira 10 LTS. We will follow up with a more precise timeline closer to the release date.

            In the meantime, the workaround for this bug is as follows:
            Increase the timeout for the calendar connection as mentioned in the [KB article JIRA|https://confluence.atlassian.com/confkb/jira-calendar-read-timed-out-312740464.html] Calendar Read Timed Out.

            Please continue watching this ticket for future updates and changes in the timeline that impacts your work.

            Best regards

            Phill Hayers
            Software Engineer
            {panel}             		New: {panel:title=Atlassian Update – 21 March 2025|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff}
            Dear Customers,

            We appreciate your effort in reporting and providing feedback regarding this issue. We are excited to inform you that the bug has been addressed in the forthcoming Confluence DC *9.4.0* version.

            This fix has been implemented in the Confluence DC and is fully compatible with all supported Jira versions. As a result, we have created a ticket CONFSERVER-99485 within the Confluence Data Center project that correctly tracks the fixed version and effectively resolves this issue.

            At the same time, please be aware that the “{_}Saved filter{_}” query option still depends on the endpoint referenced in this bug, which may render only this option unusable in larger Jira instances. The workaround is presented in the UI - the JQL query option offers a [way to search|https://confluence.atlassian.com/display/JIRASOFTWARESERVER/Advanced+searching+-+fields+reference#Advancedsearchingfieldsreference-filterFilter] by the filter keyword, which results in exactly the same result. Furthermore, we have initiated JSWSERVER-26345 to monitor this issue, specifically focusing on the affected query option.

            Best regards,

            Krystian M
            Software Engineer, Jira DC
            {panel}
            Krystian M made changes -
            Link New: This issue split to JSWSERVER-26345 [ JSWSERVER-26345 ]
            Krystian M made changes -
            Current Status Original: {panel:title=Atlassian Update – 17 September 2024|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff}
            Dear Customers,

            Thank you for taking the time to file and comment on this issue.

            We're aware that this issue is having an impact on the workflows of multiple customers and we're looking to provide a fix shortly after the release of the Jira 10 LTS. We will follow up with a more precise timeline closer to the release date.

            In the meantime, the workaround for this bug is as follows:
            Increase the timeout for the calendar connection as mentioned in the [KB article JIRA|https://confluence.atlassian.com/confkb/jira-calendar-read-timed-out-312740464.html] Calendar Read Timed Out.

            Please continue watching this ticket for future updates and changes in the timeline that impacts your work.

            Best regards

            Phill Hayers
            Software Engineer
            {panel}             		New: {panel:title=Atlassian Update – 21 March 2025|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff}
            Dear Customers,

            Thank you for taking the time to file and comment on this issue.

            We're aware that this issue is having an impact on the workflows of multiple customers and we're looking to provide a fix shortly after the release of the Jira 10 LTS. We will follow up with a more precise timeline closer to the release date.

            In the meantime, the workaround for this bug is as follows:
            Increase the timeout for the calendar connection as mentioned in the [KB article JIRA|https://confluence.atlassian.com/confkb/jira-calendar-read-timed-out-312740464.html] Calendar Read Timed Out.

            Please continue watching this ticket for future updates and changes in the timeline that impacts your work.

            Best regards

            Phill Hayers
            Software Engineer
            {panel}

              b6cf9181bff6 Krystian M
              yilinmo Yilin (Inactive)
              Affected customers:
              109 This affects my team
              Watchers:
              109 Start watching this issue

                Created:
                Updated:
                Resolved: