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
Community Members
Community Events
Community Groups

UPM: Unexpected exception parsing XML document from URL

Deleted user Jul 30, 2018

I've just upgraded to Jira (self-hosted) 7.11.1 on Linux x86_64, from version 7.3.2 and am completing the upgrade of installed plugins.

When attempting to upgrade the Atlassian Universal Plugin Manager Plugin, I get the error message:

Unexpected exception parsing XML document from URL

The logs, starting at the first 'ERROR' line with a timestamp after when I pressed the 'Update' button go as follows:

2018-07-30 16:26:15,483 ThreadPoolAsyncTaskExecutor::Thread 25 ERROR alexis 985x122x1 w835ok, /rest/plugins/1.0/ [c.a.p.osgi.factory.OsgiPlugin] Unable to start the plugin container for plugin 'com.atlassian.upm.atlassian-universal-plugin-manager-selfupdate-plugin'
org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from URL [bundle://235.0:0/META-INF/spring/atlassian-plugins-component-imports.xml]; nested exception is java.lang.IllegalStateException: The bundle is uninstalled.
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(

I've googled this, but not found anything that looked applicable. Could anybody advise? Many thanks!


1 answer

8 votes
Deleted user Jul 30, 2018

Hi Alexis,

It sounds like you might be dealing with plugin cache corruption. Are you able to uninstall the UPM and then restart the Jira instance? Additionally, you may need to clear the plugin cache, which can be done by deleting the following directories while Jira is shutdown:


All the best,

Deleted user Jul 30, 2018

I didn't see any obvious way to uninstall UPM (other plugins have an Uninstall button but not UPM), so I proceeded to clearing the cache, and that worked! Many thanks for the quick response Cameron!



I got this same error after upgrading from 7.1.9 to 7.13.2 and this fixed the issue for me as well. Thanks

thanks, @[deleted] :)

Also affected Jira 8.5.5

Solution works for me.

Please also see the Issue here:

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events