What does this Hazelcast warning indicate?

[Afkham Azeez]

WARN {com.hazelcast.nio.TcpIpConnectionManager} -  [km1.am.150.com]:4100 [km.am.150.domain] Wrong bind request from Address[elb.am.com]:5060! This node is not requested endpoint: Address[192.168.18.15]:4100 {com.hazelcast.nio.TcpIpConnectionManager}

We are seeing the above warning in some of our setups? What does this warning indicate?

Thanks

Azeez

[Peter Veentjer]

Hi Afkham,

I think I have seen this issue before but I don't know if I can give you a solution.

I guess it is related to the fact that the dns name is used in combination with ip addresses and hazelcast does a comparison based on the string content of the address and doesn't do a lookup. So when it is expected an ip address but is receiving a dns name, it gives this error.

I hope that the other Hazelcast guys can provide a solution to your problem. I'll do some searching as well. 

--
You received this message because you are subscribed to the Google Groups "Hazelcast" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hazelcast+...@googlegroups.com.
To post to this group, send email to haze...@googlegroups.com.
Visit this group at http://groups.google.com/group/hazelcast.
For more options, visit https://groups.google.com/groups/opt_out.

[Peter Veentjer]

I knew I saw something similar before.

This is an answer from Mehmet from a year ago:

Look for the title: 

Weblogic Issue: Error joining cluster (2.4-ee)

Cause of second issue is that second instance is selected '10.20.84.213' as its local address and when first node tries to connect, second replies with wrong bindrequest message. Default value of 'hazelcast.socket.bind.any' is true, so second node accepts connections to all local interfaces. You should either define '10.20.84.213' in member list or you should configure correct interface.

<tcp-ip enabled="true">

    <interface>127.0.0.1</interface>

    <interface>10.20.84.213</interface>

</tcp-ip>

OR

<interfaces enabled="true">

    <interface>10.20.84.*</interface>

</interfaces>

Can you also post debug/finest level node start logs of first issue? It should look like;

15:14:03,646  INFO [AddressPicker] - Interfaces is enabled, trying to pick one address matching to one of: [127.0.0.1]

15:14:03,647  WARN [AddressPicker] - Picking loopback address [127.0.0.1]; setting 'java.net.preferIPv4Stack' to true.

15:14:03,656 DEBUG [AddressPicker] - inet reuseAddress:true

15:14:03,658 DEBUG [AddressPicker] - Trying to bind inet socket address:/127.0.0.1:5701

15:14:03,660 DEBUG [AddressPicker] - Bind successful to inet socket address:/127.0.0.1:5701

15:14:03,661  INFO [AddressPicker] - Picked Address[127.0.0.1]:5701, using socket ServerSocket[addr=/127.0.0.1,localport=5701], bind any local is false

15:14:03,661 DEBUG [AddressPicker] - Using public address the same as the bind address. Address[127.0.0.1]:5701

@mmdogan