How to adjust default timeout ajax timeout in JSM

[#1]

Hi! 

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.

<script>
AJS.$.ajaxSetup({
timeout: 356100
});
</script>

Unfortunately,  for the JIra Service desk it does not work. Therefore I use fragments from Scriptrunner to adjust the next timeout. 

1. Open fragments https://jira.example.com/plugins/servlet/scriptrunner/admin/fragments
2. Create fragment
3. Open the portal and click Inspect in Browser and verify with next command in browser consolle:   AJS.$.ajaxSettings;  

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.

Conclusion: 

Please, vote for that ticket, if it’s helpful for you. 

https://jira.atlassian.com/browse/JSDSERVER-8515

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.

Cheers,

Gonchik Tsymzhitov

[Kishan Sharma]

Useful info @Gonchik Tsymzhitov . I have voted for the issue.

[Gonchik Tsymzhitov]

Thanks @Kishan Sharma !