Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Tempo plugin 8.11.0 can't start after restart jira 7.10.0

Michal Hlavac
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 6, 2018
2018-06-06 13:27:14,522 Spring DM Context Creation Timer WARN      [o.e.g.b.e.i.dependencies.startup.DependencyWaiterApplicationContextExecutor] Timeout occurred before finding service dependencies for [NonValidatingOsgiBundleXmlApplicationContext(bundle=com.tempoplugin.tempo-platform-jira, config=osgibundle:/META-INF/spring/*.xml)]
2018-06-06 13:27:14,610 Spring DM Context Creation Timer ERROR      [c.a.p.osgi.factory.OsgiPlugin] Plugin 'com.tempoplugin.tempo-platform-jira' never resolved service '&ao' with filter '(objectClass=com.atlassian.activeobjects.external.ActiveObjects)'
2018-06-06 13:27:14,678 Spring DM Context Creation Timer ERROR      [c.a.p.osgi.factory.OsgiPlugin] Unable to start the plugin container for plugin 'com.tempoplugin.tempo-platform-jira'
org.springframework.context.ApplicationContextException: Application context initialization for 'com.tempoplugin.tempo-platform-jira' has timed out waiting for (objectClass=com.atlassian.activeobjects.external.ActiveObjects)
        at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
        at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
        at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
        at java.util.TimerThread.mainLoop(Timer.java:555)
        at java.util.TimerThread.run(Timer.java:505)
 
2018-06-06 13:27:15,097 Spring DM Context Creation Timer ERROR      [o.e.g.b.e.internal.support.ExtenderConfiguration] Application context refresh failed (NonValidatingOsgiBundleXmlApplicationContext(bundle=com.tempoplugin.tempo-platform-jira, config=osgibundle:/META-INF/spring/*.xml))
org.springframework.context.ApplicationContextException: Application context initialization for 'com.tempoplugin.tempo-platform-jira' has timed out waiting for (objectClass=com.atlassian.activeobjects.external.ActiveObjects)
        at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
        at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
        at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
        at java.util.TimerThread.mainLoop(Timer.java:555)
        at java.util.TimerThread.run(Timer.java:505)
2018-06-06 13:27:15,111 Spring DM Context Creation Timer ERROR      [o.e.g.b.e.i.dependencies.startup.DependencyWaiterApplicationContextExecutor] Unable to create application context for [com.tempoplugin.tempo-platform-jira], unsatisfied dependencies: Dependency on [(objectClass=com.atlassian.activeobjects.external.ActiveObjects)] (from bean [&ao])
org.springframework.context.ApplicationContextException: Application context initialization for 'com.tempoplugin.tempo-platform-jira' has timed out waiting for (objectClass=com.atlassian.activeobjects.external.ActiveObjects)
        at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
        at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
        at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
        at java.util.TimerThread.mainLoop(Timer.java:555)
        at java.util.TimerThread.run(Timer.java:505)
2018-06-06 13:27:15,838 ThreadPoolAsyncTaskExecutor::Thread 17 DEBUG      [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] afterPropertiesSet

Tempo plugin 8.11.0 doesn't start on jira startup, but when jira starts, then go to Administration -> System -> Manage Addons and manually enable Tempo Timesheets addon, then it starts and work properly. I upgraded from 7.9.2 and use https://github.com/cptactionhank/docker-atlassian-jira-software docker images. thanks, m.

1 answer

0 votes
Philip Armour
Contributor
September 14, 2018

Hi Michal,

A likely reason for this is underprovisioning of the system as described here:

https://confluence.atlassian.com/jirakb/jira-applications-system-plugin-timeout-while-waiting-for-add-ons-to-enable-212173447.html?utm_medium=logScan&utm_source=STP

because the system is struggling the add-ons are not able to start-up in the available time-window when JIRA starts up, and this process times out. However when JIRA has started successfully, you can manually enable the add-ons

Hope that is helpful

Suggest an answer

Log in or Sign up to answer