Script running causing jira to become unresponsive

[Gopinath Velayudhan]

we had a major issue in our production jira instance yesterday and Jira kept becomming un-responsive after an hour. we send all the logs to Atlassian and They came back to us saying that Script running is causing this issue and they asked us to disable it.

"Looking at the stack trace error you provided : 2016-01-04 03:39:01,821 http-bio-8443-exec-200 WARN e23475 210x21708x22 gy97z6 172.30.69.189 /secure/QuickCreateIssue.jspa [jira.groovy.jql.ScriptFunctionSearchIndexer] Script runner reindexing failed on ESG-34200 It looks like this issue is caused by the 3rd party plugin called Script Runner. "

Also there was another error:

"2016-01-04 05:45:18,534 http-bio-8443-exec-13 ERROR anonymous 345x11524x6 1nzg9ci 10.6.248.157 /rest/com.onresolve.jira.plugin.Behaviours/1.0/behaviours/validators.json [common.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: Cannot get property 'name' on null object java.lang.NullPointerException: Cannot get property 'name' on null object at org.codehaus.groovy.runtime.NullObject.getProperty(NullObject.java:57) at org.codehaus.groovy.runtime.InvokerHelper.getProperty(InvokerHelper.java:169) at org.codehaus.groovy.runtime.callsite.NullCallSite.getProperty(NullCallSite.java:44) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:293) something about plugins then it starts with errors like these below : 2016-01-04 05:45:38,865 http-bio-8443-exec-95 ERROR e20264 345x11684x12 4lb1xt 172.30.71.8 /rest/viewIssue/1/remoteIssueLink/render/61160 [viewissue.issuelink.rest.RemoteIssueLinkResource] Error occurred while generating final HTML for r emote issue link: java.lang.RuntimeException: java.io.IOException: Failed to load Confluence Page from remote server Caused by: java.io.IOException: Failed to load Confluence Page from remote server Caused by: com.atlassian.sal.api.net.R esponseException: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate) Caused by: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cip her suites are inappropriate) "

I use Behaviour plugin a lot for option list manipulation. The plugin is associated to only 1 project and it is not linked to the jira project as mentioned in the first error "ESG-34200" i am not understanding why it is trying to re-index this ticket. Can you help us with this. we are kind of not stuck since we have script runner disabled.

[Thanos Batagiannis [Adaptavist]]

For the first error we will need to have a look at the logs you sent to Atlassian. Could you please create a ticket https://jamieechlin.atlassian.net/projects/GRV ?
For the second error, according to your logs, probably there is something wrong with one of your behaviours (trying to get the name from a null object). Feel free to paste any 'suspicious' behaviour in order to assist you more.

Kind regards 

[Gopinath Velayudhan]

Sure I will attach the support zip that i sent to Atalssian

[Chander Inguva]

In addition to what Thanos suggested, please check Application links between JIRA and Confluence.

[Gopinath Velayudhan]

JIra version we use is : 6.3.15 and SR version we have is: 3.0.14

[Thanos Batagiannis [Adaptavist]]

Hi Gopinath, Can I ask you which JIRA and SR versions you use ?