Details
-
Bug
-
Resolution: Not a bug
-
Medium
-
None
-
6.0.1
-
Severity 2 - Major
-
Description
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
- 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.
- Create a sample space.
- 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.
Attachments
Issue Links
- duplicates
-
CONFSERVER-45612 Support both "synchrony." and the "reza." system properties for overriding the Synchrony configuration
- Closed
- is related to
-
CONFSERVER-45567 Confluence cannot connect to Synchrony configured with non-standard -Dsynchrony.bind or -Dreza.bind
- Closed