You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Antoine Duprat (JIRA)" <se...@james.apache.org> on 2018/06/27 13:37:00 UTC
[jira] [Created] (JAMES-2443) James does not work if DNS is not
available at startup
Antoine Duprat created JAMES-2443:
-------------------------------------
Summary: James does not work if DNS is not available at startup
Key: JAMES-2443
URL: https://issues.apache.org/jira/browse/JAMES-2443
Project: James Server
Issue Type: New Feature
Components: James Core
Reporter: Antoine Duprat
h1. 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)
{code:java}
127.0.0.1 openpaas-prod.linagora.dc1 openpaas-prod
127.0.0.1 localhost
{code}
h1. Expected result
James should be able to recover.
h1. Current behaviour
It is not.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org