'java.lang.IllegalStateException: Bundle is uninstalled' error due to incompatible Add-on

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

  1. Add-on cannot be enabled in the Universal Plugin Manager(UPM).
  2. Add-on functionality may or may not be working.
  3. Accessing the Incoming Mail Handler throws an exception.

The following appears in the atlassian-jira.log:

2012-03-07 21:35:29,564 http-80-4 ERROR anonymous 1295x3x3 - 192.168.250.43 /plugins/servlet/streams [atlassian.plugin.servlet.DefaultServletModuleManager] Unable to create filter
com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.IllegalStateException: Bundle is uninstalled
	at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:152)
...
Caused by: java.lang.IllegalStateException: Bundle is uninstalled
	at org.apache.felix.framework.Felix.loadBundleClass(Felix.java:1574)

OR

An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getMailHandlers' in class com.atlassian.jira.plugins.mail.webwork.ViewMailServers threw exception java.lang.IllegalStateException: Bundle is uninstalled at /secure/admin/views/popServers.vm[line 90, column 19] at org.apache.velocity.runtime.parser.node.ASTIdentifier.execute(ASTIdentifier.java:223) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:262) at org.apache.velocity.runtime.parser.node.ASTReference.evaluate(ASTReference.java:470) at org.apache.velocity.runtime.parser.node.ASTNotNode.evaluate(ASTNotNode.java:63) at org.apache.velocity.runtime.parser.node.ASTExpression.evaluate(ASTExpression.java:62) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:85) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336) at org.apache.velocity.runtime.directive.Parse.render(Parse.java:263) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:175) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:87) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336) at org.apache.velocity.Template.merge(Template.java:328) at org.apache.velocity.Template.merge(Template.java:235) at org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:381) at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:67) at com.atlassian.jira.template.velocity.DefaultVelocityTemplatingEngine$DefaultRenderRequest.asHtml(DefaultVelocityTemplatingEngine.java:104) at

Diagnosis

If plugin related, try enabling the plugin, and watch the atlassian-jira.log for the specific stack trace above. If mail related, when accessing the incoming mail handler if the above exception is thrown it is likely caused by this behaviour.

Cause

An incompatible version of a plugin is installed. The concern here is that these errors are quite verbose and may make the log files take up considerable space on the users hard drive. A JAC case has been raised in order to fix this:  JRA-29215 - Getting issue details... STATUS

There has also been reports where this is caused by an incompatible version of the JIRA Workflow Designer Plugin. Disabling the plugin itself will not help, it has to be uninstalled and the JAR file removed

Resolution

  1. Browse to Administration >> Manage Add-ons.
  2. Find the Add-on that's disabled.
  3. Determine if this Add-on has a newer version by checking http://marketplace.atlassian.com
  4. Check the system installed Add-ons; it's possible that this Add-on has been bundled. If so, you can delete the old version.
    (info) See Bundled plugins should detect earlier versions of installed plugins and delete them for an improvement to this.
  5. If you have the Workflow Designer Plugin and it is incompatible, uninstall and remove its JAR file from the JIRA applications home directory.
  6. To remove plugin JARs, please follow these steps:
    1. Stop JIRA.
    2. Go to $JIRA_HOME/plugins/installed-plugins/
    3. Look for the plugin file in this folder and remove it.
    4. Restart your JIRA application.
Last modified on Mar 30, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.