Script Runner - Errors on JIRA startup

TechnicalS April 7, 2015

Hello,

we have a problem with the script runner.

When we start JIRA the following error occurs:


2015-03-31 10:02:47,337 Thread-24 WARN [onresolve.jira.groovy.ScriptManagerImpl] Failed to create searcher custom field. Can happen during upgrades. com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.NullPointerException at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:149) at com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:112) at com.atlassian.util.concurrent.ResettableLazyReference.get(ResettableLazyReference.java:87) at com.atlassian.jira.issue.fields.CustomFieldImpl.getCustomFieldSearcher(CustomFieldImpl.java:1809) at com.atlassian.jira.issue.fields.CustomFieldImpl.<init>(CustomFieldImpl.java:249) at com.atlassian.jira.issue.fields.CustomFieldImpl.<init>(CustomFieldImpl.java:222) at com.atlassian.jira.issue.managers.DefaultCustomFieldManager$CustomFieldCache.cloneCustomFields(DefaultCustomFieldManager.java:730) at com.atlassian.jira.issue.managers.DefaultCustomFieldManager$CustomFieldCache.getAllCustomFields(DefaultCustomFieldManager.java:717) at com.atlassian.jira.issue.managers.DefaultCustomFieldManager$CopyOnWriteCustomFieldCache.getAllCustomFields(DefaultCustomFieldManager.java:621) at com.atlassian.jira.issue.managers.DefaultCustomFieldManager.getAllCustomFields(DefaultCustomFieldManager.java:417) at com.atlassian.jira.issue.managers.DefaultCustomFieldManager.getCustomFieldObjects(DefaultCustomFieldManager.java:412) at com.atlassian.jira.issue.CustomFieldManager$getCustomFieldObjects.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)

 

2 answers

1 vote
JamieA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 7, 2015

Try disabling and enabling the plugin. This issue should be fixed in the most recent versions.

TechnicalS April 7, 2015

Hello Jamie, unfortunately it has not solve the problem. the error still occurs. What can we do now?

JamieA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 7, 2015

restart jira... that normally fixes it. What version of the plugin do you have?

TechnicalS April 7, 2015

i already restart jira but the error is still there the version is 2.1.15

TechnicalS April 8, 2015

Are you still investigating? can we can expect a solution?

JamieA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 8, 2015

jira version? Did you remove your comment: "There is a error in the admin section Global Edit Validation & Postfunction scripts are disabled due to installation problem: incompatible Quick Edit plugin."

TechnicalS April 8, 2015

JIRA Version 6.0.8 The comment was regarding to the JIRA Scipting Suite

JamieA
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 8, 2015

I'm not sure... ideally upgrade. If you can't can you try without JSS? Can you reproduce the problem in a copy of your production environment?

TechnicalS April 8, 2015

no i can not reprouce this on an other system. In the marketplace seems that only the version 2.1.15 is compatible to JIRA 6.0.8. the upgrade failed because no other version works and is compatible with JIRA 6.0.8 https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner/versions

0 votes
Benito Picarelli
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 8, 2015
TechnicalS April 8, 2015

Hello Benito, i cleared the plugin cache but the error is still there.

Suggest an answer

Log in or Sign up to answer