Small Backlog: Request Timeout when viewing Backlog

[Jackson Sardello]

Note: I'm reposting this question as I thought I had resolve the issue with an update to the JIRA Core. The issue is back a week later. Any suggestions would be appreciated.

Hello,

I've just purchased JIRA for home use. I have a small backlog (~ 100 issues) and I continually get request timeout errors when I navigate to the backlog. The frustrating this is it doesn't happen every time.....maybe 80% of the time. Sometimes I click backlog and get 3 errors before the issues pull up. Other-times it takes a dozen clicks. I have already upped the java service memory to 1GB. This did not seem to help. Any ideas?

Edit: It looks like the error is only occurring for the whole backlog. When I put on a filter, the smaller subset of cards will show up fine.

Edit 2: I've been slowly expanding the scope of my filter and have reached the point where the number of issues triggers the timeout. The exact number of backlog issues that triggers the timeout error is 72. 71 issues visible is totally fine.

[Theinvisibleman]

Hey there Jackson, this is quite unusual. Usually the timeout errors are due to having too many items to load, but in this case if it happens with just 72 issues, there may be something else at hand here.

Could you share with us what is the filter that is configured for the board/backlog right now? 

You may also want to check your JIRA logs in your Home Directory, or use the Developer Tools of the browser when the backlog is loading to see if there are any errors shown when the backlog is loading and faces the timeout.

[Jackson Sardello]

Hi Joe, thanks for taking the time to respond.

"Could you share with us what is the filter that is configured for the board/backlog right now?"

I'm not sure where to find what my backlog filter is, but it should be stock JIRA. I just created a Kanban board and started creating issues! The filter I'm using to get the timout to go away is a "No Epics" filter. It looks like this:

"Epic Link" IS EMPTY OR "Epic Link" = "EPIC1" OR "Epic Link" = "EPIC2" OR "Epic Link" = "EPIC3" or "Epic Link" = "EPIC4" or "Epic Link" = "EPIC5"

I spent some time last week trying to find something useful in the JIRA logs and didn't have any luck. I can give it another pass when I have a bit more time.

I had not thought to check my Developer Tools, although I have checked to make sure the problem isn't a browser/cookie issue. Let me know if this means anything to you, I don't do web console debugging often.

VM1330:1 GET http://192.168.1.67:8080/rest/greenhopper/1.0/xboard/plan/backlog/data.json?rapidViewId=4&selectedProjectKey=TB&_=1537204254214 net::ERR_EMPTY_RESPONSE

Thanks again for taking a look. I noticed one more odd thing that I need to test more. The error only seems to be happening for my local computer. The one that is hosting JIRA Server. When I connect to JIRA at work on a different computer, the backlog loads just fine. I will post an update when I can test this more thoroughly.