Intermittent timeout error

Issue #837 resolved
Hamilton Colyer-Long created an issue

There was an intermittent error "Unexpected error timeout" if you navigated back/forward quickly.

The gadget seems to be loading data for every data range that you scroll through. So for instance if I want data from last October and click back a bunch of times on the month view then it flashes through the data for every month between now and then. At the same time, the fact that the header jumps around as the week headers load for months you've already scrolled past, means that the icon you're clicking to navigate back a month is always moving.

Comments (6)

  1. Hamilton Colyer-Long reporter

    This report more or less duplicates the original report of #760, but in that issue you've changed the scope to being related to the pivot chart and dropped the priority to minor, whereas the behaviour I'm reporting applies to the gadget specifically and is caused by slow load times and exacerbated by the fact that unnecessary loads are occurring.

  2. Hamilton Colyer-Long reporter

    I was testing this by clicking the back button a lot of time (like 20-30) without waiting for the data to load, and then clicking "forward to current", and then back a few more times. The produced a bundle of timeout errors, after which all users are getting a "Page unavailable" error and cannot access our JIRA instance at all. I'm going to wait a few minutes to see if the site comes back, otherwise I'm going to have to contact Atlassian support to get this fixed.

    So obviously the test I was doing probably doesn't fall into the range of regular user behaviour, I was intentionally trying to see if I could get the timeout, but the fact that I could produce this, and that the consequence has affected everyone on our system is pretty dire. I don't know if it is possible to cancel data requests as people navigate before the data is fetched, or to add some delay between the button click and the data fetch, but some solution to prevent this consequence would seem necessary.

  3. Hamilton Colyer-Long reporter

    JIRA started responding again about 10 minutes later without requiring any intervention from support. But yeah I won't be testing this anymore!

  4. Log in to comment