Fix host binding of tests involving GossipRouter ------------------------------------------------ Key: JGRP-1789 URL: https://issues.jboss.org/browse/JGRP-1789 Project: JGroups Issue Type: Bug Affects Versions: 3.2.13 Environment: Windows Reporter: Richard Achmatowicz Assignee: Bela Ban Fix For: 3.2.13 Tests like TUNNEL_Test and GossipRouterTest make use of the following: - a GosspiRouter which binds to a certain host address and port - a GossipRouter client whose TUNNEL protocol binds to a certain host address and port If these bind addresses are not specified, we often get test failures involving an inability of the client to communicate with the GossipRouter. {noformat} ------------- startRouter ----------- -- starting GossipRouter on 127.0.0.1[23003] ------------- testConnectThree ----------- ------------------------------------------------------------------- GMS: address=B, cluster=TUNNEL_Test, physical address=192.168.5.141:61373 ------------------------------------------------------------------- 605382 [WARN] TUNNEL: - Failed connecting to GossipRouter at /127.0.0.1:23003 605383 [WARN] TUNNEL: - failed reconnecting stub to GR at /127.0.0.1:23003: java.lang.Exception: Could not connect to /127.0.0.1:23003 605383 [ERROR] TUNNEL: - failed sending message to cluster (94 bytes): java.lang.Exception: None of the available stubs [RouterStub[localsocket=/192.168.5.141:51802,router_host=127.0.0.1::23003,connected=false]] accepted a multicast message, cause: null {noformat} TUNNEL_Test and GossipRouterTest are failing on Windows, for example, due to this sort of issue.