Delay in Confluence Startup Due to Synchrony

[moeinfaked]

Dear Team,

I am experiencing an issue while running Confluence Data Center on my server, where the startup process is delayed by approximately 60 minutes. During this period, only a series of Synchrony-related logs are displayed, and after this time, Confluence starts successfully.

This delay appears to be caused by issues with the Synchrony Proxy, which fails to start properly, resulting in error messages similar to the following in the logs:




2025-02-03 17:16:42,364 WARN [synchrony-interop-scheduled-executor:thread-2] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:8090/synchrony-proxy/healthcheck]: Connect to 127.0.0.1:8090 [/127.0.0.1] failed: Connection refused: no further information 2025-02-03 17:17:12,869 WARN [synchrony-interop-scheduled-executor:thread-2] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:8090/synchrony-proxy/healthcheck]: Connect to 127.0.0.1:8090 [/127.0.0.1] failed: Connection refused: no further information 2025-02-03 17:17:34,733 ERROR [pool-36-thread-1] [agent.service.featureflag.Fx3OkhttpAdapter] post Error occurred while making post request with message : Connect timed out . Returning empty FeatureFlag Set from Fx3 Service 2025-02-03 17:17:43,373 WARN [synchrony-interop-scheduled-executor:thread-2] [plugins.synchrony.bootstrap.DefaultSynchronyProxyMonitor] pollHealthcheck Could not ping the synchrony-proxy [http://127.0.0.1:8090/synchrony-proxy/healthcheck]: Connect to 127.0.0.1:8090 [/127.0.0.1] failed: Connection refused: no further information

I am using Embedded Synchrony and have not configured an external Synchrony instance.

Server Specifications & Configuration:

• Confluence Version: Data Center 8.5.8
• Operating System: Windows Server 2022 (Running in a Virtual Machine - 4 Sockets, 12-Core CPU, 24GB RAM)
• Database: MySQL
• Allocated Memory (JVM Heap): e.g., Xms4g Xmx10g
• Using Embedded Synchrony? Yes
• Firewall Enabled? Yes

Questions:

1. What is causing this 60-minute startup delay, and how can I resolve it?
2. My Confluence has recently been consuming excessive CPU resources, leading to performance issues and user dissatisfaction. Could this be related to the Synchrony problem?

I appreciate your guidance in resolving these issues.

Best regards,

[Mirek]

Hi @moeinfaked 

So looking at the logs this is the main problem 

Could not ping the synchrony-proxy [http://127.0.0.1:8090/synchrony-proxy/healthcheck]: Connect to 127.0.0.1:8090 [/127.0.0.1] failed: Connection refused: no further information

I would start by temporalny disabling firewall ans see if there is any improvement.. 

This is a loopback addrees so making sure that machine can also talk with itself is very important. 

As for high CPU.. Yes, it could be all connected. Making sure that startup procedure is fine and synchrony is working correctly would show if there is still problem so I would recommend focus first on that.