You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
In that article, I will show how to adjust default ajax timeout for JSD portal and will request manageable functionality from Atlassian :)
So that story starts from long-running timeouts request and small performance degradation.
That instance is used for the 30k active users and works on Jira Service Desk Data Center release on 3 nodes.
And sometimes our users are met with next errors.
After observation in first time it was quite complicated to reproduce it.
Of course, I checked monitoring what’s happened.
You can see that Jira SM has a default timeout of 60 sec.
Early, I used the next KB “How to change the default ajax timeout on Jira server” which works well for Jira software, and Jira Core.
Add into the announcement banner the next info.
Unfortunately, for the JIra Service desk it does not work. Therefore I use fragments from Scriptrunner to adjust the next timeout.
I used the next query in ELK to review logs and check graphs: url~ "POST /servicedesk/customer/portal/?/create/”
For creating request action we can use adjusted timeout.
Please, vote for that ticket, if it’s helpful for you.
Because that parameter looks needful if Jira used for the different users (locations, slow connectivity) and during performance degradation easier you can adjust and evaluate. Also, some rest api can be especially long than constant timeout 60 sec.