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

With the the system property synchrony.proxy.enabled is set (to true), the proxy won't be enabled after a Tomcat restart until we restart Synchrony

    XMLWordPrintable

Details

    Description

      Tomcat is not able to start the synchrony-proxy webapp before Confluence does the healthcheck on the proxy (race condition). Therefore, Confluence fails to enable the proxy mode and still uses the original /synchrony path and original port (8091 by default).

      Workaround

      Restart Synchrony in the Confluence's Collaborative Editing screen will enable the internal proxy mode again.

      Attachments

        Issue Links

          was split into

          Suggestion - CONFSERVER-45272 Use HTTP and localhost as the scheme and hostname when checking the proxy webapp's running state

          • Closed

          Suggestion - CONFSERVER-45273 Remove the healthcheck for the synchrony-proxy webapp when Confluence is started up and monitor the proxy's running status

          • Closed
          mentioned in

          Page Loading...

          Activity

            People

              ttranminh Tam Tran
              ttranminh Tam Tran
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 8h
                  8h
                  Remaining:
                  Remaining Estimate - 8h
                  8h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified