Error creating bean with name 'automaticTransitionLimiterImpl'

Christopher Cheng October 14, 2017

After upgrading from 7.3 to 7.5, the system started up with this plugin error.

Is it safe to remove this plugin?

 

 

g.springframework.beans.factory.BeanCreationException: Error creating bean with name 'automaticTransitionLimiterImpl': Instantiation of bea Failed to instantiate [com.atlassian.jira.plugin.triggers.impl.transition.AutomaticTransitionLimiterImpl]: No default constructor found; ns.impl.transition.AutomaticTransitionLimiterImpl.<init>()
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFacto
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.jav
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:77
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:8
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$1600(AbstractDelegatedExecution
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplic
at org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecu
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTa
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.atlassian.jira.plugin.triggers.impl.transition.va.lang.NoSuchMethodException: com.atlassian.jira.plugin.triggers.impl.transition.AutomaticTransitionLimiterImpl.<init>()
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:85)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.
... 17 more
Caused by: java.lang.NoSuchMethodException: com.atlassian.jira.plugin.triggers.impl.transition.AutomaticTransitionLimiterImpl.<init>()
at java.lang.Class.getConstructor0(Class.java:3082)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:80)
... 18 more
2017-10-14 22:33:19,542 ThreadPoolAsyncTaskExecutor::Thread 40 ERROR [o.e.g.b.e.i.dependencies.startup.DependencyWaiterApplicationConta-transition-triggers-plugin], unsatisfied dependencies: none
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'automaticTransitionLimiterImpl': Instantiation of b Failed to instantiate [com.atlassian.jira.plugin.triggers.impl.transition.AutomaticTransitionLimiterImpl]: No default constructor found; ns.impl.transition.AutomaticTransitionLimiterImpl.<init>()
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFacto
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.jav
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:77
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:8
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$1600(AbstractDelegatedExecution
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplic
at org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecu
at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTa
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.atlassian.jira.plugin.triggers.impl.transition.va.lang.NoSuchMethodException: com.atlassian.jira.plugin.triggers.impl.transition.AutomaticTransitionLimiterImpl.<init>()
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:85)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.
... 17 more
Caused by: java.lang.NoSuchMethodException: com.atlassian.jira.plugin.triggers.impl.transition.AutomaticTransitionLimiterImpl.<init>()
at java.lang.Class.getConstructor0(Class.java:3082)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:80)
... 18 more

1 answer

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 16, 2017

Hi Christopher,

That error is not commonly seen.   It looks like that specific code package is in reference to Jira's ability to automatically trigger workflow changes, such as from when someone pushes a code change to a repo that Jira is connected to such as with Bitbucket or Github.   I wouldn't recommend just removing that plugin, as it could break other dependencies, even if you are not using this functionality currently:

  1. To rule out any possible incompatible plugins causing the issue, please temporarily move out all the files under $JIRA_HOME/plugins/installed-plugins to another location, then restart JIRA.
  2. If issue still persists, please provide us the output of the following SQL query:
    SELECT * FROM pluginstate;

It is possible there is something in your environment causing this plugin to fail to load in Jira, but with the snippet of logs, we can't exactly see what that might be.   If it's another plugin, then step 1 should resolve this.   If this plugin has become disabled in the database, then it would be listed in this SQL select statement, which could be preventing it from working as expected.  

Please try these steps and provide us this info, if we still cannot see a clear cause after this, we will likely want to create a support request on your behalf.

Regards,
Andy

Suggest an answer

Log in or Sign up to answer