msg/async: truly use first addr if multiple incoming addrs provided

For incoming IPv4 and IPv6 dual stack support, there might be
multiple addresses provided in entity's addrvec.
The comment says we'll just pick whichever is listed first for now
to accept, whereas the implementation does quite the opposite.

Signed-off-by: xie xingguo <xie.xingguo@zte.com.cn>

diff --git a/src/msg/async/AsyncMessenger.cc b/src/msg/async/AsyncMessenger.cc
index 959e76f77787e80eb4449b2fa615c9e4b9fdcc26..d2737608c70840f16677fd2cf6e9c88213a64e22 100644 (file)
--- a/src/msg/async/AsyncMessenger.cc
+++ b/src/msg/async/AsyncMessenger.cc
@@ -578,6 +578,7 @@ AsyncConnectionRef AsyncMessenger::create_connect(
     // FIXME: for ipv4 vs ipv6, check whether local host can handle ipv6 before
     // trying it?  for now, just pick whichever is listed first.
     target = a;
+    break;
   }
 
   // create connection