Portfolio for Jira disabled after update

Marc Weiland_cpzvwn

Hi,

after updating Portfolio for Jira to the latest version, the app is disabled and enabling the app runs into the following error:

505x10810x2 az713v /rest/plugins/1.0/installed-marketplace [o.e.g.b.e.internal.support.ExtenderConfiguration] Application context refresh failed (NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.jpo, config=osgibundle:/META-INF/spring/*.xml))
org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from URL [bundle://258.0:0/META-INF/spring/portfolio-root-context.xml]; nested exception is java.lang.IllegalStateException: The bundle is uninstalled.
	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:414)
	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336)
	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304)
	at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:187)
	at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:223)
	at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:194)
	at org.eclipse.gemini.blueprint.context.support.OsgiBundleXmlApplicationContext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:171)
	at org.eclipse.gemini.blueprint.context.support.OsgiBundleXmlApplicationContext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:141)
	at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:133)
	at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:619)
	at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$800(AbstractDelegatedExecutionApplicationContext.java:57)
	at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$3.run(AbstractDelegatedExecutionApplicationContext.java:239)
	at org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
	at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.startRefresh(AbstractDelegatedExecutionApplicationContext.java:217)
	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.stageOne(DependencyWaiterApplicationContextExecutor.java:224)
	at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.refresh(DependencyWaiterApplicationContextExecutor.java:177)
	at org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.refresh(AbstractDelegatedExecutionApplicationContext.java:154)
	at org.eclipse.gemini.blueprint.extender.internal.activator.LifecycleManager$1.run(LifecycleManager.java:213)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

Any idea on how to solve this issue?

This is running on Jira Software 8.0.1 (Server). 

Any help is greatly appreciated. Thank you.

Andy Heinzer

Hi Marc,

Sorry to hear you are having this problem with Portfolio.  The specific stacktrace you posted would seem to indicate that the plugin you have installed in your Jira is actually incompatible, at least per our KB in 'java.lang.IllegalStateException: Bundle is uninstalled' error due to incompatible Add-on.

There are a few things here that might be complicating factors though.  Your specific version of Jira, 8.0.1, was pulled from downloads and marketplace.  The Jira Release notes do make a note about this in https://confluence.atlassian.com/jirasoftware/issues-resolved-in-8-0-1-966679555.html

It was removed because of a bug that would pretty badly impede Service Desk when using a MS SQL database on the backend.  More details about this in JSDSERVER-6253

 

Even if you're not affected by that bug, the fact that Atlassian pulled this release has other side affects in regards to installing plugins from Marketplace.  Namely, the fact that you can't typically find any plugins in the UPM in Jira that will show as being compatible, or you can't download these directly from Jira at least.  Which likely means you have to download them manually from the Marketplace website and then upload them into the UPM yourself.  If you follow this method, you might have downloaded the data center version of this plugin instead of the server version or vice versa.  You can see all the versions for both platforms in the page https://marketplace.atlassian.com/apps/1212136/portfolio-for-jira/version-history

 

1. If you did grab the wrong one, you should be able to fix this by
2. Stop Jira
3. remove the plugin from the $JIRAHOME/plugins/installed-plugins/ directory
4. run the following query against the Jira database
   select * from pluginstate;
5. If you find any entries for portfolio in that table, we can remove these to clear any disabled flags that might prevent components needed for portfolio to start up.
6. Then start Jira
7. Then we can use the manage addons to manually upload the correct plugin version.

 

Ideally, I would want to use the "Find new apps' link to install this plugin, but I don't think this is going to work with your pulled release of 8.0.1.  So It might be a good idea to upgrade Jira to a 8.0.2 or 8.1.0 version that is not affected by this pulled release problem.  This could help us to make sure your Jira version is actually getting the correct version of that plugin that will work with your system.

Please let me know if you have any problems with this.

Andy