[JAMES-1999] JAMES do not delayed startup on not yet started ElasticSearch

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0
• Assignee: Unassigned
• Reporter: Quynh Nguyen
• Created: 14/Apr/17 02:44
• Updated: 25/May/17 02:28
• Resolved: 25/May/17 02:28

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.