de.communardo.confluence.plugins.apc addon prevents Confluence 7 from starting

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

After upgrading to Confluence 7, startup fails with the following error:

1 2 java.lang.NullPointerException at de.communardo.confluence.plugins.apc.filter.APCRedirectAndMetaTagFilter.doFilter(APCRedirectAndMetaTagFilter.java:39)

Environment

Confluence 7.4

Accessibility for Confluence addon version 2.1.1

Diagnosis

Run the following SQL query to confirm this plugin is installed, either in an enabled or disabled state:

1 SELECT from plugindata where pluginkey ='de.communardo.confluence.plugins.apc';

Cause

The 2.1.1 version of this plugin is not compatible with Confluence 7, and if present, will cause this error upon startup after you upgrade to Confluence 7.

Solution

Option 1

Prior to upgrading to Confluence 7, upgrade the "Accessibility for Confluence" addon to the latest version so that a compatible version will be present once Confluence 7 loads for the first time.  

Option 2

Always back up your data before making any database modifications. If possible, test any alter, insert, update, or delete SQL commands on a staging server first.

If you've already upgraded, please do the following:

  • Stop Confluence 

  • Delete the plugin from the database by issuing the following SQL statement:

1 DELETE from plugindata where pluginkey ='de.communardo.confluence.plugins.apc';
  • Start Confluence, verify it will start successfully now

  • (optional) Install the latest version of the plugin to restore its functionality or leave it uninstalled if no longer used. 

Note: If you cannot disable this addon using the "Plugin Map" method described in How to remove malfunctioning addons, it may be because the plugin was enabled and never once disabled prior to the upgrade to Confluence 7 and thus will have no entry in the Plugin Map to set to "false". If this is the case, delete it from the PLUGINDATA table as described above. 

Updated on March 10, 2025

Still need help?

The Atlassian Community is here for you.