Faster Permissions Service cannot be enabled due to corrupted group name

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

Faster permission service was introduced since Confluence 7.16 to achieve better performance.

However, an error like below may occur in application log (atlassian-confluence.log), when enabling it.

1 2 2022-05-31 16:47:50,526 ERROR [pool-12-thread-9] [security.denormalisedpermissions.impl.DenormalisedChangeLogListenerBase] updateAllRecords Content service: unable to update all permissions: java.lang.IllegalStateException: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: We got user or group name 'xyz' from database even though we haven't requested it. It seems it's a bug java.util.concurrent.ExecutionException: java.lang.IllegalStateException: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: We got user or group name 'xyz' from database even though we haven't requested it. It seems it's a bug

Cause

This issue should be caused by corrupted group name. Especially, it may happen when there are trailing blank characters (trailing spaces etc.) in a group name.

Solution

Check if there is any corrupted group names in any tables of https://confluence.atlassian.com/confkb/how-to-rename-a-group-and-preserve-its-permissions-948228977.html

If any wrong group name is found, run the update SQL in the KB to correct them.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.