Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,363,136
Community Members
 
Community Events
168
Community Groups

Upgrade problems to Service Management 4.20.1: Plugins fail to start

I have a JIRA Server that has Software and Service management on it. I recently upgraded Software to 8.20.1. I tried to upgrade Service Management to 4.20.1, but the upgrade did not go well at all. A lot of the plugins for Service Management fail to start. 

I've tried:

* Uninstalling and re-installing via the web UI

* Clearing the plugin caches

* Extending the time out to 600 seconds (that makes for a loooong boot)

None of these seem to help. Does anyone have any ideas? 

 

Below is a clip from the logs:

2021-11-02 23:18:36,279-0400 Spring DM Context Creation Timer ERROR      [c.a.p.osgi.factory.OsgiPlugin] Plugin 'com.atlassian.jira.jira-issue-nav-components' never resolved service '&beanBuilderFactory' with filter '(&(objectClass=com.atlassian.jira.rest.v2.issue.builder.BeanBuilderFactory)(objectClass=com.atlassian.jira.rest.v2.issue.builder.BeanBuilderFactory))'

2021-11-02 23:18:36,279-0400 Spring DM Context Creation Timer ERROR      [c.a.p.osgi.factory.OsgiPlugin] Unable to start the plugin container for plugin 'com.atlassian.jira.jira-issue-nav-components'

org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.jira.issue-nav-components' has timed out waiting for (&(objectClass=com.atlassian.jira.rest.v2.issue.builder.BeanBuilderFactory)(objectClass=com.atlassian.jira.rest.v2.issue.builder.BeanBuilderFactory))

        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.base/java.util.TimerThread.mainLoop(Unknown Source)

        at java.base/java.util.TimerThread.run(Unknown Source)

2021-11-02 23:18:36,285-0400 Spring DM Context Creation Timer ERROR      [o.e.g.b.e.internal.support.ExtenderConfiguration] Application context refresh failed (NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.jira.issue-nav-components, config=osgibundle:/META-INF/spring/*.xml))

org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.jira.issue-nav-components' has timed out waiting for (&(objectClass=com.atlassian.jira.rest.v2.issue.builder.BeanBuilderFactory)(objectClass=com.atlassian.jira.rest.v2.issue.builder.BeanBuilderFactory))

        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.base/java.util.TimerThread.mainLoop(Unknown Source)

        at java.base/java.util.TimerThread.run(Unknown Source)

2021-11-02 23:18:36,285-0400 Spring DM Context Creation Timer ERROR      [o.e.g.b.e.i.dependencies.startup.DependencyWaiterApplicationContextExecutor] Unable to create application context for [com.atlassian.jira.issue-nav-components], unsatisfied dependencies: Dependency on [(&(objectClass=com.atlassian.jira.rest.v2.issue.builder.BeanBuilderFactory)(objectClass=com.atlassian.jira.rest.v2.issue.builder.BeanBuilderFactory))] (from bean [&beanBuilderFactory])

org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.jira.issue-nav-components' has timed out waiting for (&(objectClass=com.atlassian.jira.rest.v2.issue.builder.BeanBuilderFactory)(objectClass=com.atlassian.jira.rest.v2.issue.builder.BeanBuilderFactory))

        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.base/java.util.TimerThread.mainLoop(Unknown Source)

        at java.base/java.util.TimerThread.run(Unknown Source)

2021-11-02 23:18:36,572-0400 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.atlassian.jira.jira-projects-plugin, config=osgibundle:/META-INF/spring/*.xml)]

2021-11-02 23:18:36,573-0400 Spring DM Context Creation Timer ERROR      [c.a.p.osgi.factory.OsgiPlugin] Plugin 'com.atlassian.jira.jira-projects-plugin' never resolved service '&servletForwarder' with filter '(&(objectClass=com.atlassian.web.servlet.api.ServletForwarder)(objectClass=com.atlassian.web.servlet.api.ServletForwarder))'

2021-11-02 23:18:36,573-0400 Spring DM Context Creation Timer ERROR      [c.a.p.osgi.factory.OsgiPlugin] Unable to start the plugin container for plugin 'com.atlassian.jira.jira-projects-plugin'

org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.jira.jira-projects-plugin' has timed out waiting for (&(objectClass=com.atlassian.web.servlet.api.ServletForwarder)(objectClass=com.atlassian.web.servlet.api.ServletForwarder))

        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.base/java.util.TimerThread.mainLoop(Unknown Source)

        at java.base/java.util.TimerThread.run(Unknown Source)

2021-11-02 23:18:36,581-0400 Spring DM Context Creation Timer ERROR      [o.e.g.b.e.internal.support.ExtenderConfiguration] Application context refresh failed (NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.jira.jira-projects-plugin, config=osgibundle:/META-INF/spring/*.xml))

org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.jira.jira-projects-plugin' has timed out waiting for (&(objectClass=com.atlassian.web.servlet.api.ServletForwarder)(objectClass=com.atlassian.web.servlet.api.ServletForwarder))

        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.base/java.util.TimerThread.mainLoop(Unknown Source)

        at java.base/java.util.TimerThread.run(Unknown Source)

2021-11-02 23:18:36,582-0400 Spring DM Context Creation Timer ERROR      [o.e.g.b.e.i.dependencies.startup.DependencyWaiterApplicationContextExecutor] Unable to create application context for [com.atlassian.jira.jira-projects-plugin], unsatisfied dependencies: Dependency on [(&(objectClass=com.atlassian.web.servlet.api.ServletForwarder)(objectClass=com.atlassian.web.servlet.api.ServletForwarder))] (from bean [&servletForwarder])

org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.jira.jira-projects-plugin' has timed out waiting for (&(objectClass=com.atlassian.web.servlet.api.ServletForwarder)(objectClass=com.atlassian.web.servlet.api.ServletForwarder))

        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.base/java.util.TimerThread.mainLoop(Unknown Source)

        at java.base/java.util.TimerThread.run(Unknown Source)

 

2 answers

Hello, we are experiencing the same issues. Is there a resolution??

Same problem here but with JSM 4.20.2 + Jira Software 8.20.2. Sometimes it boots fine, sometimes not. Restarting the service does the trick... but something is not fine here. 

Here at WSU, in our test environment we are experiencing a similar issue since upgrading to 4.20.7/8.20.7 from 4.13.2/8.13.2. Every time we update a plugin its takes Jira down. We have to reboot server to get it to come back up again. We will not be upgrading production until this is resolved.

I am looking forward to a fix. Thanks for this post. 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events