Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-59121

Editing or Creating Jira Issue Date Filters timing out with Team Calendars

    XMLWordPrintable

Details

    Description

      Summary

      Attempting to edit the JIRA Issue Dates filter or create a Jira Issue Dates event on Team Calendars often results in a long delay and eventual timeout when the connected Jira instance contains a large volume of projects and configuration. The UI then fails to display the filter details and no editing can occur.

      Steps to Reproduce

      1. Navigate to a Team Calendar with Jira Issues Dates associated with Projects, Custom Fields, etc..
      2. In the list of Event Types, select one to modify and select Edit... (or in the case of Create Event, click on the Add Event button or on the calendar itself)
      3. The edit dialogue will appear and a spinning progress indicator will be shown. Eventually the, progress indicator will disappear and no details of the filter can be edited.

      Expected Results

      • Filter returns and can be edited

      Actual Results

      • The progress indicator disappears and editing is not possible. The following error is logged by Confluence
      2018-01-19 23:41:28.984 ERROR com.atlassian.confluence.extra.calendar3.rest.ExceptionMappers.GeneralExceptionMapper General exception happen on calendar resources java.net.SocketTimeoutException: Read timed out com.atlassian.sal.api.net.ResponseException: java.net.SocketTimeoutException: Read timed out at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:100) at com.atlassian.plugins.rest.module.jersey.JerseyRequest.executeAndReturn(JerseyRequest.java:131) at com.atlassian.applinks.core.auth.ApplicationLinkRequestAdaptor.execute(ApplicationLinkRequestAdaptor.java:58) at com.atlassian.applinks.oauth.auth.OAuthRequest.execute(OAuthRequest.java:58) at com.atlassian.confluence.extra.calendar3.calendarstore.DefaultJiraAccessor.getQueryOptionsInternal(DefaultJiraAccessor.java:218) at com.atlassian.confluence.extra.calendar3.calendarstore.DefaultJiraAccessor.lambda$null$0(DefaultJiraAccessor.java:197) at com.atlassian.vcache.internal.core.metrics.TimedSupplier.get(TimedSupplier.java:32) at com.atlassian.vcache.internal.core.service.DefaultRequestCache.lambda$get$2(DefaultRequestCache.java:52) at java.util.Optional.orElseGet(Optional.java:267) at com.atlassian.vcache.internal.core.service.DefaultRequestCache.get(DefaultRequestCache.java:50) at com.atlassian.vcache.internal.core.metrics.TimedLocalCacheOperations.get(TimedLocalCacheOperations.java:64) at com.atlassian.confluence.impl.vcache.metrics.vertigostartup.VertigoStartupMonitoringRequestCache.get(VertigoStartupMonitoringRequestCache.java:36) at com.atlassian.confluence.extra.calendar3.calendarstore.DefaultJiraAccessor.lambda$getQueryOptions$1(DefaultJiraAccessor.java:197) at java.util.Optional.map(Optional.java:215) at com.atlassian.confluence.extra.calendar3.calendarstore.DefaultJiraAccessor.getQueryOptions(DefaultJiraAccessor.java:196) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) 

      No Workaround

      Attachments

        Issue Links

          Activity

            People

              lhou1 Lorien Hou
              gkeefer Greg Keefer (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: