nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Slowness problem after upgrade of behaviours

Florent_SCARAVETTI

Hello,

after JIRA upgrade from 5.0.7 to 6.4.12 with upgrade of behaviours plugin (from behaviour 0.5.0 to script runner 4.1.3.9), we have important slowness problem. When edit issue screen is displayed, server requests done by script runner plugin (by URLs http://<server_host>:8080/rest/com.onresolve.jira.plugin.Behaviours/1.0/behaviours/validators.json and http://<server_host>:8080/rest/com.onresolve.jira.plugin.Behaviours/1.0/behaviours/runvalidator.json) take several seconds (almost 30 seconds).

With previous version of behaviours plugin, server request took always less than 1 second.

Slowness only concerns behaviours functions.No slowness has been observed on other functions of script runner or JIRA functions.

atlassian-jira_6.4.12.log

Roles_for_test_mcc.png

atlassian-jira_6.4.12_allroles.log

atlassian-jira_5.0.7.log

Accepted answers

All comments

Kristian Walker _Adaptavist_

Hi Florent,

Could you please advise if you have tried restarting the server following the upgrade and if not please perform a restart to see if this resolves the issue.

Also you could you please perform the following actions for me so we can help you to diagnose the cause of this error.

Restart the JIRA Server
Perform a full re index on the JIRA server.
Run the JIRA Integrity Checker and provide a screenshot of the results that this outputs.
Attach a copy of the atlassian-jira.log file from when you experience the behaviours running slowly.

Many Thanks

Kristian Walker

Florent_SCARAVETTI

Hi Kristian,

I followed all the 4 steps, slowness is still present for behaviours.

I sent you and .

Many thanks for your help.

Florent Scaravetti

atlassian-jira.log

Integrity_checker_screenshot.png

Kristian Walker _Adaptavist_

Hi Florent,

Could you please try fixing the errors flagged up by the Integrity Checker.

Also i notice in the log that your are getting lots of user admin(admin) must be in role errors which is causing behaviours to execute lots of permission checks. Can you please review the log and ensure the user is added to each role mentioned to see if that resolves the slowness issues.

Thanks

Kristian

Florent_SCARAVETTI

Hi Kristian,

Errors returned by integrity checker have been fixed (there is no change relative to slowness). You can fing of an edit operation before JIRA upgrade (only 1 second) and of an edit operation after JIRA upgrade (30 seconds). User and issue are the same in the two cases.

I tried to add a user to all project roles (not a functional case), it's a little faster (4 seconds). Log file is .

Thanks,

Florent

Kristian Walker _Adaptavist_

Hi Florent,

Can you please confirm if the User is now added to all project roles?

Also can you confirm that if this is the case that the behaviours are now taking 4 seconds to run?

I am seeing from your last log file lots of errors saying user test_mcc(test_mcc) must be in role XXX.

Can you please try adding all users to all project roles to see if this fixes the issue.

It looks to me as this issue has been caused by your upgrade from JIRA 5.0.7 to 6.4.12 which has broken users project roles and is what is causing lots of permission checks to be made and is filling up the logs.

Thanks

Kristian

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

addon-com.onresolve.jira.groovy.groovyrunner