Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-45565

Confluence cannot connect to Synchrony configured with non-standard -Dsynchrony.port

      When Confluence is started with -Dsynchrony.port=8092 or something other than 8091, Synchrony starts up on the indicated port, but Confluence is unable to contact Synchrony.

      Confluence ought to be using synchrony.port when it constructs the 'Synchrony Internal Service URL. However it doesn't:

      [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] updateSynchronyConfiguration Synchrony External Base URL: http://localhost:8090/synchrony-proxy
      [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] updateSynchronyConfiguration Synchrony External Service URL: http://localhost:8090/synchrony-proxy/v1
      [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] updateSynchronyConfiguration Synchrony Internal Service URL: http://localhost:8091/synchrony/v1
      [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] updateSynchronyConfiguration Synchrony Resources URL: http://localhost:8090/synchrony-proxy/resources
      
      

      resulting in later editor failures:

      [plugins.synchrony.config.DefaultSynchronyConfigurationManager] postConfigToSynchrony [Collab editing plugin] Synchrony connection failure: Could not generate/verify AppID/Secret for real-time collaboration service at http://localhost:8091/synchrony/v1
      [plugins.synchrony.config.DefaultSynchronyConfigurationManager] postConfigToSynchrony [Collab editing plugin] Synchrony connection failure: Could not generate/verify AppID/Secret for real-time collaboration service at http://localhost:8091/synchrony/v1
      
      

      Steps to replicate

      1. Start a new Standalone Confluence with -Dsynchrony.port=8092, e.g.:
        cd /tmp
        tar xf path/to/atlassian-confluence-6.0.2.tar.gz 
        cd atlassian-confluence-6.0.2/
        CATALINA_OPTS="-Dconfluence.home=$(pwd)/confhome -Dsynchrony.port=8092" ./bin/catalina.sh run
        
        

         # Choose an install with sample data, set a license key and create an admin user.

      1. Create a sample space.
      2. You will be left in an editor with a spinner, and the 'Loading the editor's taking longer than usual' error.

      Workaround

      Use -Dreza.port instead, which is used by Synchrony and correctly incorporated into the Synchrony Internal Service URL.

            [CONFSERVER-45565] Confluence cannot connect to Synchrony configured with non-standard -Dsynchrony.port

            Hello, We are now encountering this type of problem. We are running our confluence on a Windows 10 20H2 device. I already tried to change to -Dreza.port in setenv.sh and even in regedit java but still cannot change the synchrony port. Can anyone help me on this? Thank you.

            Neil Anthony Morada added a comment - Hello, We are now encountering this type of problem. We are running our confluence on a Windows 10 20H2 device. I already tried to change to -Dreza.port in setenv.sh and even in regedit java but still cannot change the synchrony port. Can anyone help me on this? Thank you.

            This is currently expected behaviour, as 'synchrony.port' has not been set up to work with Confluence Server. We are adding that functionality though, and the work is being tracked in CONF-45612.

            Denise Unterwurzacher [Atlassian] (Inactive) added a comment - This is currently expected behaviour, as 'synchrony.port' has not been set up to work with Confluence Server. We are adding that functionality though, and the work is being tracked in  CONF-45612 .

              Unassigned Unassigned
              7c5359af675b Jeff Turner
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: