-
Suggestion
-
Resolution: Duplicate
-
None
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
After an upgrade or even after an unclean shutdown of Confluence it is very likely that the plugin cache gets corrupted, which causes LazyReference$InitializationException: java.lang.NullPointerException errors on startup.
This can be fixed by clearing the plugin cache, however many support tickets could be avoided by having this performed automatically on each startup or at least after an upgrade. The negative impact would be a slightly longer startup.
Note: There is also a related bug for this situation that's been logged at CONFSERVER-52749
- duplicates
-
CONFSERVER-21174 When confluence starts, empty the content of the plugins-temp folder
- Future Consideration
- relates to
-
CONFSERVER-52749 Cannot start Confluence due to corrupt plugin cache
- Closed
-
CONFCLOUD-26519 Clear plugin cache after an upgrade / possibly on every startup
- Closed