Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Instance does not start with TCP config in 2.5 when hosts are not reachable #523

Closed
peterlitvak opened this issue Jun 27, 2013 · 1 comment

Comments

Projects
None yet
2 participants
@peterlitvak
Copy link

commented Jun 27, 2013

When using the TCP-IP config if there is a host listed that was never registered by the DNS available to the current host (one that starts with this config) the initialization throws an exception:

--(snippet)---
java.net.InetAddress.getAllByName(InetAddress.java:1063)
at com.hazelcast.impl.AddressPicker.resolveDomainNames(AddressPicker.java:216)
--(snippet)---<

Note that exception is not thrown if the hosts are listed by IP addresses even if there is an IP address that was never registered with DNS.

This pertains only to the host names that where never registered with DNS or registration of which expired. If host is down but can be looked up by name no exception is thrown.

@pveentjer

This comment has been minimized.

Copy link
Member

commented Jun 27, 2013

I'm able to reproduce the problem using:

public class Foo {

    @Test
    public void test() {
        Config config = new Config();
        Join join = config.getNetworkConfig().getJoin();
        join.getMulticastConfig().setEnabled(false);
        join.getTcpIpConfig().setEnabled(true);
        join.getTcpIpConfig().addMember("hazelcast.banana");

        HazelcastInstance hz = Hazelcast.newHazelcastInstance(config);
        System.out.println("Instance created");
    }
}

@pveentjer pveentjer closed this in 7ea1431 Jun 27, 2013

mdogan added a commit that referenced this issue Jun 27, 2013

Merge pull request #525 from pveentjer/fix/2.x/host-not-reachable
Fixes #523: instance doesn't start when one of the addresses is not reac...

@ghost ghost assigned pveentjer Jun 27, 2013

mdogan added a commit that referenced this issue Jun 27, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.