ScriptRunner: BUG! exception in phase 'semantic analysis' in source unit 'Script40.groovy' Bundle is uninstalled

[Mathias Schindler]

Hi,

I am using Jira 6.3.3 and ScriptRunner 3.0.4. When I'm trying to run a little script using the script console I get the following error:

BUG! exception in phase 'semantic analysis' in source unit 'Script41.groovy' Bundle is uninstalled at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:927)

I found out that it must have something to do with the imports. For example:

import com.atlassian.jira.issue.Issue;

println "test"
log.error "test"

will bring up the error message whereas:

println "test"
log.error "test"

runs without any issue. Maybe someone knows whats wrong here.

Best regards
Mathias

[JamieA · Accepted solution]

That's a bit weird... try disabling and enabling the plugin?

[francis]

Got the same thing but cycling the addon is not resolving the problem, which is happening since we installed the service desk add-on This stack trace is raised when you have a 'commentvalidator' script in your workflow transition. The full stack trace is http://pastebin.com/B4Sj2Ak1

[JamieA]

So when SD is disabled, no problem, as soon as you re-enable, problem?

[francis]

This is a production system - so I can't experiment. I removed the commentvalidator from the workflow, which obviously resolved the symptom. Will try to reproduce on test system.

[Neil Nelson]

Disabling and then re-enabling fixed the problem for me; thank you for the suggestion.

[Srinivas Marripudi]

Same for me, disabling and then re-enabling the Script Runner add-on, worked for me !! Thanks Jamie

[Mathias Schindler]

Thank you, your hint solved the problem.

[Gezim Shehu [Communardo]]

Disabling , Re enabling the plugin. (in my case updating also) fixed the issue.

This bug really should be adressed as it's the 2nd time it has happened in our production system, unpredictably.

[Darren Wright]

We had the same issue, we disabled/re-enabled the ScriptRunner plugin and it fixed our issue.

[Rob Targosz]

I am getting a similar error after upgrading:

BUG! exception in phase 'semantic analysis' in source unit 'bundle://158.0:0/com/onresolve/scriptrunner/canned/jira/workflow/conditions/CustomScriptCondition.groovy' Bundle is uninstalled

This groovy script doesn't even exist in the plugin jar.

[Roy Chapman]

I got the same error After upgrading to JIRA 6.3.12.  This occured when user was trying to access an issue.  Nothing else, just access

Referer URL: Unknown
BUG! exception in phase 'semantic analysis' in source unit 'bundle://152.0:0/com/onresolve/scriptrunner/canned/jira/workflow/conditions/SimpleScriptedCondition.groovy' Bundle is uninstalled
BUG! exception in phase 'semantic analysis' in source unit 'bundle://152.0:0/com/onresolve/scriptrunner/canned/jira/workflow/conditions/SimpleScriptedCondition.groovy' Bundle is uninstalled

I upgraded a number of plugins at the same time as upgrading, but not script runner.  I disabled/enabled and this problem went away.  Just thought I would add this in case people see similar.

[JamieA]

Hello Roy. Accessing an issue will check the conditions, in your case your workflow must use Simple Scripted Condition. So try the solution...