JWME throwing errors after an upgrade to 6.4.0 / Jira Server

[web]

setup:

- Jira 7.12
- MyGroovy is also installed (1.18.1)

after a JWME upgrade to 6.4.0:
any workflow with setting a value in a post function - failed with this:

2020-12-20 17:16:50,877 http-nio-8080-exec-14 ERROR xxxxxx /secure/QuickCreateIssue.jspa [c.innovalog.groovy.GroovyExpression] [Class:SetFieldValueFunction ; Workflow:xxxxxx; Transition:1 ; Is
sue:xxxxxx] Groovy Script threw error:                                                                                                               
com.google.common.util.concurrent.ExecutionError: BUG! exception in phase 'instruction selection' in source unit 'script_9555e3a5716dd83c1826686b79cf9c6e.groovy' org.codehaus.groovy.ast.ModuleNode cannot be cast to org.codehaus.groovy.ast.AnnotationNodeCaused by: java.lang.ClassCastException: org.codehaus.groovy.ast.ModuleNode cannot be cast to org.codehaus.groovy.ast.AnnotationNode                  
        at org.codehaus.groovy.transform.sc.StaticCompileTransformation.visit(StaticCompileTransformation.java:52)                                
        at org.codehaus.groovy.transform.ASTTransformationVisitor$3.call(ASTTransformationVisitor.java:318)                                             
        at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:965)                                   
        ... 293 more                                                                                                                                  
2020-12-20 17:16:50,886 http-nio-8080-exec-14 ERROR      [o.a.c.c.C.[.[localhost].[/].[action]] Servlet.service() for servlet [action] in context with path [] threw exception [Servlet execution threw an exception] with root cause
java.lang.ClassCastException: org.codehaus.groovy.ast.ModuleNode cannot be cast to org.codehaus.groovy.ast.AnnotationNode                               
        at org.codehaus.groovy.transform.sc.StaticCompileTransformation.visit(StaticCompileTransformation.java:52)

disabling MyGroovy fixed these issues.
does it point to conflicting Groovy versions? or similar?
thanks!

[Nic Brough -Adaptavist-]

It's saying that you have a groovy script that is no longer valid for the current API - this might be the actual script, but it looks more like MyGroovy isn't working for this version of Jira.  Check the compatibility of the current version of the app.

[web]

thanks!

well - it did not complain before my JMWE upgrade to 6.4.0. and MyGroovy I have is the most recent available version and has not been messed with.

Is there a way to check what Groovy versions are used in both plugins? unpacking a jar, looking for a specific class?

[Nic Brough -Adaptavist-]

That implies your script is calling something in JMWE, a class that has changed such that it can't use it any more.

[David Fischer]

It does look like an incompatibility between JMWE and MyGroovy. From which version of JMWE did you upgrade? Also, did you try to restart Jira to see if it fixes the issue?

[web]

6.3.5 -> 6.4.0
no, did not try to restart yet... waiting for another maintenance window

thank you