[JAMES-2443] James does not work if DNS is not available at startup

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: James Core
• Assignee: Unassigned
• Reporter: Antoine Duprat
• Created: 27/Jun/18 13:36
• Updated: 04/Jul/18 02:38
• Resolved: 04/Jul/18 02:38

Description

Description

When James starts and DNS is not available (in this case for resolving the ES nodes IP), James does not succeed to recover even when the DNS is back.
The DNS was also set in /etc/hosts, but in a format that is maybe unsuitable (same IP on multiple lines)

127.0.0.1       openpaas-prod.linagora.dc1 openpaas-prod
127.0.0.1   localhost

Expected result

James should be able to recover.

Current behaviour

It is not.