Uploaded image for project: 'James Server'
  1. James Server
  2. JAMES-1999

JAMES do not delayed startup on not yet started ElasticSearch

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.0.0
    • Component/s: None
    • Labels:
      None

      Description

      We had implemented the delayed start for James. When launching James + Cassandra +ES, James is supposed to wait sometimes for Cassandra and ElasticSearch when they are not yet started. This allow rebooting
      components in any order. This especially useful in docker-compose, or
      when your infrastructure do handle service dependencies.

      This feature appeared to be buggy.

      We will:

      • Implement integration tests demonstrating this behavior
      • Extract the underlying retry service and unit test it.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              qnguyen Quynh Nguyen
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: