Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,367,902
Community Members
 
Community Events
168
Community Groups

Scriptrunner errors after upgrading to 4.* version

Hi There,

 

We've updated to the latest available version of Scriptrunner for our 6.4.7 JIRA version and now I see errors in the log file:

2018-02-01 09:50:01,372 atlassian-scheduler-quartz1.clustered_Worker-1 ERROR automation [atlassian.scheduler.core.JobLauncher] Scheduled job with ID 'com.onresolve.jira.groovy.groovyrunner:EscalationService-job:-266997063' failed
groovy.lang.GroovyRuntimeException: Ambiguous method overloading for method com.atlassian.jira.security.JiraAuthenticationContextImpl#setLoggedInUser.
Cannot resolve which method to invoke for [null] due to overlapping prototypes between:
[interface com.atlassian.crowd.embedded.api.User]
[interface com.atlassian.jira.user.ApplicationUser]
at groovy.lang.MetaClassImpl.chooseMostSpecificParams(MetaClassImpl.java:3238)
at groovy.lang.MetaClassImpl.chooseMethodInternal(MetaClassImpl.java:3191)
at groovy.lang.MetaClassImpl.chooseMethod(MetaClassImpl.java:3134)
at groovy.lang.MetaClassImpl.getMethodWithCachingInternal(MetaClassImpl.java:1330)
at groovy.lang.MetaClassImpl.createPojoCallSite(MetaClassImpl.java:3367)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.createPojoSite(CallSiteArray.java:132)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.createCallSite(CallSiteArray.java:166)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125)
at com.onresolve.scriptrunner.canned.jira.admin.EscalationService.runService(EscalationService.groovy:406) <+2> (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$PogoCachedMethodSiteNoUnwrapNoCoerce.invoke(PogoMetaMethodSite.java:210)
at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(PogoMetaMethodSite.java:59)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:166)
at com.onresolve.scriptrunner.canned.jira.admin.EscalationService.execute(EscalationService.groovy:334)
at com.onresolve.scriptrunner.canned.jira.admin.EscalationService$execute$0.callCurrent(Unknown Source)
at com.onresolve.scriptrunner.canned.jira.admin.EscalationService.runJob(EscalationService.groovy:432)
at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:136)
at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:101)
at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:80)
at com.atlassian.scheduler.quartz1.Quartz1Job.execute(Quartz1Job.java:32)
at org.quartz.core.JobRunShell.run(JobRunShell.java:223)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)

I can't understand where they are coming from. 

Any help is appreciated, thanks. 

 

4 answers

1 vote

I seem to remember this cropping up a while ago, internally.  Try raising it with the SR team at https://productsupport.adaptavist.com/servicedesk/customer/portal/2

Appears to be from EscalationServices settings. Increased interval stopped errors from appearing in log file. However manual running does not produce any errors. 

Anyone? Any ideas? 

In Installed plugins there is only one version of scriptrunner:

ls installed-plugins/ | grep -i groo
plugin.5844083495313701053.groovyrunner-4.1.3.24.jar

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events