Problem Definition

Often, on startup or on Add-on update Confluence has errors with Add-Ons that have versions that clash with each other. This often causes issues for customers and support tickets.

Please also see related bug

• CONFSERVER-52749: Cannot start Confluence due to corrupt plugin cache

In atlassian-confluence.log we can see errors like

2017-07-22 21:28:39,769 WARN [localhost-startStop-1] [osgi.container.felix.FelixOsgiContainerManager] doLog Unable to resolve bundle 226: Unresolved constraint in bundle net.customware.confluence.plugin.scaffolding [226]: Unable to resolve 226.0: missing requirement [226.0] package; (&(package=org.randombits.confluence.metadata)(version>=7.4.1)(!(version>=8.0.0))) [caused by: Unable to resolve 229.0: missing requirement [229.0] package; (&(package=org.randombits.supplier.core.annotate)(version>=1.0.9)(!(version>=1.1.0)))]

Another example is when running version 4 of ScriptRunner and upgrading to version 5.

• ScriptRunner for Confluence

Only clearing the plugin cache does not always resolve this issue.

Suggested Solution

Have better version checks in the plugin loader for incompatible versions.

Workaround

This is documented here for the ScriptRunner issue

• Updating Adaptavist ScriptRunner for Confluence stops and locks Add-Ons

For other plugins, remove the plugin from the database directly

1. Shutdown Confluence
2. Check the logs and query the database to determine the correct plugin to remove

   select plugindataid, pluginkey, filename, lastmoddate from plugindata;
   

3. Remove the plugin from the database

   delete from plugindata where pluginkey = '<pluginkey>';
   

4. Update bandana table (if required)

   update bandana set bandanavalue = '<map/>' where bandanakey = 'plugin.manager.state.Map';
   

5. Clear the plugin cache
   • How to clear Confluence plugins cache
6. Restart Confluence

Notes

This is a related bug

• CONFSERVER-52749: Cannot start Confluence due to corrupt plugin cache