Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Time out error when click on some issues move to bottom of backlog.

Mandia July 8, 2018

I'm selecting about 20-30 issues in backlog, click on Move to Bottom of Backlog, and get timed out error.

Does anyone knows what's the root cause about this issueTime out error.PNG

1 answer

1 accepted

0 votes
Answer accepted
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 9, 2018

Hello Mandia,

There are a few things to check out.

First look at the atlassian-jira.log and the atlassian-greenhopper.log to see if there are any explicit stack trace errors that can give some additional info on the cause of the timeout error.

Next Run the LexoRank management console Integrity checks as covered in This Article to see if there are any integrity issues identified,  as well as run the troubleshooting steeps covered In This KB especially the max rank length SQL query to see if the rebalance operations are completing successfully:

SELECT "FIELD_ID", max(length("RANK")) AS max_rank_string_length FROM "AO_60DB71_LEXORANK" GROUP BY "FIELD_ID";

Regards,
Earl

Mandia July 10, 2018

Thanks for reply me.

The root cause of this issue is that I select too many issues.

Thanks,

Mandia

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events