Often, on startup, especially on an upgrade, the plugin cache can become corrupted with invalid Add-Ons. This often causes issues for customers and support tickets.
Please note the similar bug
In atlassian-confluence.log we can see errors like
Error like these may also appear
should be completely deleted on restart.
For support we often have to ask customers to do this when we see OSGI version errors, or other side effects after start up causing instability.
- there may be a left over jar file from a removed Add-On still in the plugin directory that Confluence tries to load
- On upgrade from Java 7 to Java 8 the jar files need to be completely rebuilt
Support will usually point customers to one of these documents
This is a related bug, where an Add-On is invalid on upgrade and needs to be removed from the database and disk
- Shut down Confluence
- Delete the all the files and folders in (may need adjusting for your environment)
- <confluence.home>/bundled-plugins_language (might not exist)
- Restart Confluence