Uploaded image for project: 'Bamboo'
  1. Bamboo
  2. BAM-20075

Shutdown due to server outage should not have unhandled exceptions

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Gathering Impact (View Workflow)
    • Priority: Low
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Agents
    • Labels:
      None

      Description

      Problem Definition

      When a remote agent loses the connectivity with the Bamboo server it tries to reconnect 5 times and then shuts down the wrapper.
      The error messages are not easy to read in the logs and includes stack traces with 502 errors caused by the agent failed attempts to get the fingerprint.
      Server outages are expected and should be shown in the logs with graceful messages, not recurrent stack traces with errors that might lead to time wasted investigations.

      Suggested Solution

      When restarting the JVM, the agent should check if the Bamboo server is online and if no response is received it should clearly states in the logs that the Bamboo server didn't answer and could be offline. The message should not include unnecessary stack traces.

      Both linux and windows behaviors can be seen below in the comments

      Related content:

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              dsantos Daniel Santos
              Votes:
              4 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated: