Synchrony Enabling Shared Drafts warning repeats in Confluence logs

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

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

Problem

Confluence reports a WARN message that Synchrony is enabling shared drafts every 10 seconds. The following appears in atlassian-confluence.log:

 2019-03-23 22:11:33,584 WARN [ListenableFutureAdapter-thread-0] [plugins.synchrony.config.DefaultSynchronyConfigurationManager] enableSharedDrafts [Collab editing plugin] Enabling Shared Drafts
 2019-03-23 22:11:48,063 WARN [ListenableFutureAdapter-thread-0] [plugins.synchrony.config.DefaultSynchronyConfigurationManager] enableSharedDrafts [Collab editing plugin] Enabling Shared Drafts
 2019-03-23 22:12:01,863 WARN [ListenableFutureAdapter-thread-0] [plugins.synchrony.config.DefaultSynchronyConfigurationManager] enableSharedDrafts [Collab editing plugin] Enabling Shared Drafts
 2019-03-23 22:12:14,309 WARN [ListenableFutureAdapter-thread-0] [plugins.synchrony.config.DefaultSynchronyConfigurationManager] enableSharedDrafts [Collab editing plugin] Enabling Shared Drafts
 2019-03-23 22:12:28,496 WARN [ListenableFutureAdapter-thread-0] [plugins.synchrony.config.DefaultSynchronyConfigurationManager] enableSharedDrafts [Collab editing plugin] Enabling Shared Drafts
 2019-03-23 22:12:41,227 WARN [ListenableFutureAdapter-thread-0] [plugins.synchrony.config.DefaultSynchronyConfigurationManager] enableSharedDrafts [Collab editing plugin] Enabling Shared Drafts
 2019-03-23 22:12:53,987 WARN [ListenableFutureAdapter-thread-0] [plugins.synchrony.config.DefaultSynchronyConfigurationManager] enableSharedDrafts [Collab editing plugin] Enabling Shared Drafts
 2019-03-23 22:13:06,997 WARN [ListenableFutureAdapter-thread-0] [plugins.synchrony.config.DefaultSynchronyConfigurationManager] enableSharedDrafts [Collab editing plugin] Enabling Shared Drafts
 2019-03-23 22:13:20,586 WARN [ListenableFutureAdapter-thread-0] [plugins.synchrony.config.DefaultSynchronyConfigurationManager] enableSharedDrafts [Collab editing plugin] Enabling Shared Drafts
 2019-03-23 22:13:33,746 WARN [ListenableFutureAdapter-thread-0] [plugins.synchrony.config.DefaultSynchronyConfigurationManager] enableSharedDrafts [Collab editing plugin] Enabling Shared Drafts
 2019-03-23 22:13:45,708 WARN [ListenableFutureAdapter-thread-0] [plugins.synchrony.config.DefaultSynchronyConfigurationManager] enableSharedDrafts [Collab editing plugin] Enabling Shared Drafts

The Synchrony process appears to be functioning correctly as page edits and creation are stable for end users despite the flood of the WARN messages.

Diagnosis

Environment

  • Confluence

  • Collaborative Editing turned on (powered by Synchrony) 

Diagnostic Steps

  1. Run the following grep to check for the count of these messages. If the result is a high number, it indicates a high number of duplicate WARNs for this message: 

    grep -c 'Enabling Shared Drafts' atlassian-confluence.log
  2.  Check the atlassian-synchrony.log file for a bind exception. (info) Note that this example has been pared down for brevity and the actual stack trace reported may be much longer: 

    2019-03-25 15:59:27,910 DEBUG [291:StdOutHandler [/path/to/Confluence/jar]] {"synchrony":{"message":"synchrony.logging [error] uncaught exception","ns":"synchrony.logging","throwable":"clojure.lang.ExceptionInfo: Error in component :
    Caused by: java.net.BindException: Address already in use\n\tat sun.nio.ch.Net.bind0(Native Method)\n
  3. We need to verify the status of the java processes running on the host. You should only see two process IDs, one for Confluence and one for Synchrony respectively. If you are affected by this issue, you will return two unique process IDs for Synchrony in your results: 

    ps -ef | grep java

Cause

You may see this flood of messages if Confluence is detecting a secondary Synchrony process. Sometimes a Confluence shutdown may not properly terminate the Synchrony process with it. Consequently on a subsequent start up, Confluence will instantiate the Synchrony process which effectively creates a duplicate Synchrony process and creates this behavior. 

Resolution

We will need to kill the extraneous Synchrony process and restart Confluence and Synchrony to remove the messages and maintain a singular Synchrony process: 

  1. Stop Confluence
  2. run ps -ef | grep java once more to confirm that the extra synchrony process is still up.
  3. Kill this extra process by running kill -9 <PID HERE>
  4. Clear Confluence Plugin Cache
  5. Restart Confluence


DescriptionSynchrony Enabling Shared Drafts warning repeats in Confluence logs
ProductConfluence
Last modified on Apr 5, 2019

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.