Install on 5.2.6 (download) fails for Script Runner 2.1-BETA-8

[Christian Jennewein]

Running JIRA 5.2.6 (Download version) I fail to enable the plugin after install from marketplace:

This plugin failed to enable. Your license may be invalid. Please refer to the logs for more information.

The audit logs say: Failed to enable plugin Script Runner (com.onresolve.jira.groovy.groovyrunner)

Any idea what went wrong?

Hi Jamie, thanks for your quick reply.

Here's the log of our server for the installation, what do you think?

2013-02-15 16:19:30,486 pool-30-thread-3 INFO n.blanc 1056x56449x1 km8844 91.238.131.187,10.11.1.1,10.11.1.4 /rest/plugins/1.0/available [atlassian.plugin.loaders.ScanningPluginLoader] Plugin Unit: /space/atlassian/application-data/jira/plugins/installed-plugins/plugin.3602012641656161741.groovyrunner-2.1-BETA-8.jar (1360941565000) created

2013-02-15 16:19:30,680 pool-30-thread-3 INFO n.blanc 1056x56449x1 km8844 91.238.131.187,10.11.1.1,10.11.1.4 /rest/plugins/1.0/available [atlassian.plugin.util.WaitUntil] Plugins that have yet to be enabled: [com.onresolve.jira.groovy.groovyrunner], 60 seconds remaining

2013-02-15 16:19:30,915 Spring executor 25 ERROR n.blanc 1056x56449x1 km8844 91.238.131.187,10.11.1.1,10.11.1.4 /rest/plugins/1.0/available [plugin.osgi.factory.OsgiPlugin] Unable to start the Spring context for plugin com.onresolve.jira.groovy.groovyrunner

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'scriptManager' defined in URL [bundle://109.0:0/META-INF/spring/atlassian-plugins-components.xml]: Instantiation of bean failed; nested exception is java.lang.VirtualMachineError: out of space in CodeCache for adapters

at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:254)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:925)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:835)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)

at java.security.AccessController.doPrivileged(Native Method)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)

at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)

at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)

at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)

at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)

at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)

at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:429)

at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:728)

at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.access$1600(AbstractDelegatedExecutionApplicationContext.java:69)

at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:355)

at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)

at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)

[JamieA · Accepted solution]

Not really... can you restart jira and see if that works? If not, we'll need the logs to understand what's going on.

You might need to create a ticket on https://jamieechlin.atlassian.net/browse/GRV.

[Christian Jennewein]

Thanks for your immediate reply, Jamie! I just updated the ticket with the logs, does it give any hint regarding the installation failure?

Thanks in advance,
Christian

[JamieA]

I think this issue is https://jamieechlin.atlassian.net/browse/GRV-56 - try setting the vm argument and restarting.

[Christian Jennewein]

Restarting did the trick, the plugin is now enabled. Thanks for your help Jamie!

[Christian Jennewein]

Thanks for all your feedbacks. We'll restart our JIRA tonight to see if this fixes the issue.

[Andreas Decker]

Do I have to change the VM settings or is it already sufficient to restart jira?

[JamieA]

Probably change your jvm settings, although restarting might be sufficient....

[Andreas Decker]

Unfortunately we can't restart our system at the moment.

I just checked the logfile:

Unable to start the Spring context for plugin com.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'scriptManager' defined in URL [bundle://140.0:0/META-INF/spring/atlassian-plugins-components.xml]:

Instantiation of bean failed; nested exception is java.lang.VirtualMachineError:

out of space in CodeCache for adapters at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:254)

[JamieA]

OK it is the same error - I'm afraid it's not going to work til you restart jira.

[Andreas Decker]

G'Day!

We are using Jira 5.2.4 and have the same problem.

After the installation from the market we get

This add-on failed to enable. It may require a license...

Then it wont let enable itself :-/

Are there any suggestions how we can get the script runner onto our system?

Thank you!

Best Regards

Andreas Decker

[JamieA]

Is it really the same problem as above, ie do you see the message: "out of space in CodeCache for adapters" in your log?

Does restarting help?