These are some generic tips and techniques to help resolve plugin installation or licensing problems. In many cases, installation problems are not specific to the plugin, but instead relate to general usage or issues with the Atlassian Universal Plugin Manager (UPM) or the underlying plugin system. Generally speaking, most recent versions of plugins on this site are built using Atlassian's plugin 2 framework and all paid plugins use Atlassian licensing support. Installation is provided by UPM. Licensing support is also provided by UPM except for older versions of UPM. If these tips don't resolve your issue, it is likely you will need to open an Atlassian support ticket. 

Installation Problems

Plugin disabled

Users may report macros no longer working in Confluence or similar problems with JIRA or Bamboo. The plugin may have become disabled because of installation of other plugins or for other reasons. See UPM-2893 for instance.

Resolution steps

  1. Go to UPM
  2. Enable all the plugins that should be enabled
  3. If plugin still cannot be enabled:
    1. Uninstall the plugin
    2. Re-install the plugin
    3. You may need to re-install the license
  4. If plugin still cannot be enabled:
    1. Consider restarting the server
    2. Look in your server logs for installation errors and clues
    3. Depending on the information you find, either open a support issue with Atlassian support (UPM) or plugin vendor (something indicating it is specific to the plugin)


Confluence only. Plugins automatically install the RB components at a version required by the plugin to operate. Do not manually downgrade them! This will cause other plugins to become disabled. Unfortunately, UPM asks you to downgrade them if the are not properly marked in the Marketplace compatibility matrix (UPM-3535). ServiceRocket has updated the support matrix in Marketplace.

If you have inadvertently updated any of these components, then follow the step #3 below. An alternative is to use a previous version of the affected plugin that has different dependencies.

What is an obr?

Previously, most plugins shipped as jar files. Now it seems many are obr files. What is the difference and what do I need to know about this?

  1. An obr is an OSGi Bundle Repository. In simple terms, it contains the normal plugin jar file plus jar files for component plugins that are required
  2. It is installed via UPM the same as a jar file
  3. Most Bob Swift Software Confluence plugins contain a number of component plugins that are required for the plugin to work
  4. The UPM manages the installation of all the required plugins provided they are not already installed at minimum level required by the using plugin
  5. When installed, these component plugins show up in UPM like other plugins
  6. While these component plugins can be updated independently, normally plugin administrators should just worry about installing the primary plugin
  7. Plugin administrators should not disable these component plugins as will cause the using plugin to be disabled or not work as expected

What are these RB plugins?

For Confluence, Bob Swift Software takes advantage of some base enablers provided by a set of RB (formerly randombits) components supported by ServiceRocket. When a plugin gets installed, the RB components also get installed. Think of them as necessary plumbing. Generally, you should not have to worry about them. Never downgrade them!

Current, the following RB components are needed by most Bob Swift Software Confluence plugins.


 After installing or removing plugins in Confluence, there can be errors reported like: 


com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.IllegalStateException: Cannot autowire object because the Spring context is unavailable.


This is a UPM/plugin framework issue with mismatched class versions of some license management code. Likely related to some other UPM or plugin upgrade or install that has occurred. Reference is UPM-3306.  

javax.servlet.ServletException: Servlet execution threw an exception
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:313)

caused by: java.lang.LinkageError: loader constraint violation: when resolving interface method "com.atlassian.upm.api.license.PluginLicenseManager.getLicense()Lcom/atlassian/upm/api/util/Option;" the class loader (instance of org/apache/felix/framework/ModuleImpl$ModuleClassLoader) of the current class, com/atlassian/upm/license/storage/lib/ThirdPartyPluginLicenseStorageManagerImpl$1, and the class loader (instance of org/apache/felix/framework/ModuleImpl$ModuleClassLoader) for resolved class, com/atlassian/upm/api/license/PluginLicenseManager, have different Class objects for the type com/atlassian/upm/api/util/Option used in the signature
    at com.atlassian.upm.license.storage.lib.ThirdPartyPluginLicenseStorageManagerImpl$1.call(ThirdPartyPluginLicenseStorageManagerImpl.java:61)

Service proxy has been destroyed

org.springframework.osgi.service.importer.ServiceProxyDestroyedException: service proxy has been destroyed

Other OSGI plugin related problems


Plugin not working after upgrade

The add-on failed to enable. org.osgi.framework.BundleException: Unresolved constraint in bundle

Table problems

Tables missing Common table capabilities expected from Advanced Tables for ConfluenceSQL for Confluence, or similar plugins. 

 Resolution Steps

  1. Go to UPM and look for the Table Library for Bob Swift Add-ons plugin as: Bob Swift Software - Table Sorter Library.

  2. Make sure it is enabled! If not, enable it!


Installation Tips

It is strongly recommended users update to the latest UPM level before installing new plugins or upgrades.

After installing a plugin, review your plugin list to ensure plugins are properly enabled (UPM-2893). Note additional component plugins that automatically got installed as an fyi.