-
Suggestion
-
Resolution: Obsolete
-
XPSP3 32 bits, Tomcat 6.029 JDK sun 32 bits 1.6.22, Confluence 3.4.1 final
-
12
-
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
The folder confluence-home\plugins-temp seems to be used by at least the non bundled plugins to extract some libraries they depend on and which are packaged in the corresponding jar in META-INF/lib.
I have compared the content of this folder for a couple of plugins available from the plugin manager search menu or directly from the authors (calendar, cache, linking, multi-excerpt).
My understanding is that this is the standard way to add dependent jars to a confluence plugin, the plugin framework taking care of extracting them to confluence-home\plugins-temp when required.
The issue if that EACH time the server/confluence starts (or the plugin reinstalled I guess), it does it.
As an example on a DEV server I have <<616>> files in this folder corresponding in fact to the same 8 jars, 77 versions of each of them!!!
This server is not restarted everyday and this is a good thing or we would have 10, 20 or 30 times more files.
You need to do something.
This folder can be part of a backup and this is no good to waste disk space for nothing.
I simply suggest when confluence starts to clear the content of the folder.
Note: There is also a related bug for this situation that's been logged at CONFSERVER-52749
- is caused by
-
CONFCLOUD-27034 Redeploy plugins on each startup, and provide options for admins to clear the plugin cache through the front end
- Closed
- is duplicated by
-
CONFCLOUD-26519 Clear plugin cache after an upgrade / possibly on every startup
- Closed
- is related to
-
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