JIRA and Confluence Page Load Times is Extremely High with Crowd SSO Enabled

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

Symptoms

After enabling Crowd SSO, JIRA and Confluence Page Load Times become extremely high.

Diagnosis

Crowd SSO is connected to Bamboo, Stash, and FeCru but only JIRA and Confluence is affected.

Cause

Locks on the cwd_token table are not being released back to the pool. Related bug repots:

CWD-3692 - Crowd freezes under heavy load

CWD-3688 - Transaction errors due to cwd_token constraint violation

Solution

Workaround

Workaround is to switch to in-memory session storage:

Session Configuration

Updated on April 17, 2025

Still need help?

The Atlassian Community is here for you.