-
Bug
-
Resolution: Done
-
Major
-
4.0.15
-
None
This is a follow-up to JGRP-2296 - which changed `DefaultDNSResolver.java` to preserve the port for SRV records. While that change is working as desired, `DNS_PING.java` is not using the port when doing member discovery.
Here are the log entries using 4.0.15
2018-11-29 21:37:41,561 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-4,null,null) Entries collected from DNS (in 5 ms): [172.29.11.50:27106, 172.29.11.50:27105] 2018-11-29 21:37:41,562 DEBUG [org.jgroups.protocols.dns.DNS_PING] (thread-4,null,null) 982d38761cba: sending discovery requests to hosts [172.29.11.50:27106, 172.29.11.50:27105] on ports [7600 .. 7600]
Since the port was found via the SRV record, it should be used instead of the transportPort port.
- is duplicated by
-
JGRP-2300 DNS_PING in AWS ECS cannot cluster with dynamic port mappings
- Closed