Confluence has a small number of obscure configuration and debugging settings that can be enabled through Java system properties. System properties are usually set by passing the -D
flag to the Java virtual machine in which Confluence is running.
Property |
Since |
Possible Values |
Module... |
Effect |
confluence.home |
1.0 |
Any filesystem path |
Confluence and atlassian-config |
If this system property is set, Confluence will ignore the contents of the confluence-init.properties file, and use this property as the setting for the Confluence Home directory. |
confluence.devmode |
1.0 |
true |
Confluence |
Enables additional debugging options that may be of use to Confluence developers. Do not enable this flag on a production system. |
atlassian.forceSchemaUpdate |
1.0 |
true |
atlassian-config |
By default, Confluence will only run its database schema update when it detects that it has been upgraded. This flag will force Confluence to perform the schema update on system startup. |
confluence.ignore.debug.logging |
1.0 |
true |
Confluence |
Confluence will normally log a severe error message if it detects that DEBUG level logging is enabled (as DEBUG logging generally causes a significant degradation in system performance). Setting this property will suppress the error message. |
confluence.i18n.reloadbundles |
1.0 |
true |
Confluence |
Setting this property will cause Confluence to reload its i18n resource bundles every time an internationalised string is looked up. This can be useful when testing translations, but will make Confluence run insanely slowly. |
atlassian.disable.caches |
2.4 |
true |
atlassian-plugins, atlassian-cache-servlet |
Setting this property will disable conditional get and expires: headers on some web resources. This will significantly slow down the user experience, but is useful in devlopment if you are frequently changing static resources and don't want to continually flush your browser cache. |