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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi Community!
When troubleshooting slowness or contentions in Jira we usually rely on Thread dumps.
When there's a ScriptRunner Groovy script involved, it shows up in the Thread's Stracktrace in an aliased form:
Script2$_run_closure1.doCall(Script2.groovy:21)
My question is if there's a way to trace which script exactly is this "Script2". Are these aliases stored somewhere in the database, available through API or somewhere in the UI we learn which Groovy script is that?
Cheers!
If you are uncertain which code the error is pointing to, I suggest you look into the classes/ folder, i.e. <JIRA_HOME>/scriptrunner/classes/ folder, e.g. /var/lib/atlassian/application-data/jira/scriptrunner/classes/, search for the class file with that name there and try to decompile it.
Once you have the decompiled code, try to locate a similar code in your environment. You could use the Script Registry to perform the search.
I hope this helps to answer your question. :-)
Thank you and Kind regards,
Ram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.