Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-9710

Remote events between Bitbucket Server and Bamboo/JIRA/FishEye don't work immediately after restart

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 4.14.3
    • 3.1.0, 4.13.0
    • Enterprise
    • None

      Summary

      After an application link is defined between two applications, remote events are only sent from one application to the other after the capabilities of the applications have been shared. This discovery happens consistantly while the applications are running. Restarting both applications however, causes a temporary failure because the first discovery attempt will usually fail if the target application doesn't start quickly enough. This is not problematic by itself but the discovery attempts occur with an exponential delay.

      Steps to Reproduce

      1. Install Bitbucket Server.
      2. Install Bamboo.
      3. Set up an application link between Bamboo and Bitbucket Server.
      4. And a repo in Bamboo.
      5. Confirm that remote events are getting sent by Bitbucket Server.
      6. Stop both Bitbucket Server and Bamboo.
      7. Start Bitbucket Server and then start Bamboo.

      Expected Results

      Remote events are sent from Bitbucket Server to Bamboo.

      Actual Results

      Since Bamboo isn't available immediately, Bitbucket Server waits to check its capabilities again, which in turn delays remote events.

      Workaround

      For customers on versions < 4.14.3 set either one of the following system properties will fix the problem:

      • navlink.failurecache.backoff=2
      • navlink.failurecache.maxExpiryMs=1

            [BSERV-9710] Remote events between Bitbucket Server and Bamboo/JIRA/FishEye don't work immediately after restart

            james_m_brown1210241387 added a comment -

            Is this supposed to be down in the bitbucket.properties file

            For customers on versions < 4.14.3 set either one of the following system properties will fix the problem:

            • navlink.failurecache.backoff=2
            • navlink.failurecache.maxExpiryMs=1

            james_m_brown1210241387 added a comment - Is this supposed to be down in the bitbucket.properties file For customers on versions < 4.14.3 set either one of the following system properties will fix the problem: navlink.failurecache.backoff=2 navlink.failurecache.maxExpiryMs=1

              rfriend rikf
              moles Marcin Oles
              Affected customers:
              0 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: