Performance Problems due to Cluster Communication

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

This article applies to Confluence clustered 5.4 or earlier.

Symptoms

When taking a thread dump, some threads look like:

1 2 3 4 5 6 7 8 9 10 11 12 13 Thread: TP-Processor40 state=object_wait java.lang.Object.wait java.lang.Object.wait com.tangosol.net.cache.OverflowMap$Status.waitForAvailable com.tangosol.net.cache.OverflowMap.prepareStatus com.tangosol.net.cache.OverflowMap.beginKeyProcess com.tangosol.net.cache.OverflowMap.getInternal com.tangosol.net.cache.OverflowMap.get com.tangosol.coherence.component.util.CacheHandler.getLease com.tangosol.coherence.component.util.CacheHandler.getCachedResource com.tangosol.coherence.component.util.CacheHandler.get com.tangosol.coherence.component.util.SafeNamedCache.get com.atlassian.confluence.cache.tangosol.TangosolCache.get

Cause

Nodes in the cluster are not communicating.

Resolution

See Data Center Troubleshooting. If you are on a version prior to Confluence 3, consider an upgrade. Performance has been greatly improved in that version.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.