The WFLY-16423 fix doesn't seem to have fixed the problem on IPv4, only IPv6. As a result:

https://ci.wildfly.org/project.html?projectId=WF_MainNightlyJobs&buildTypeId=&tab=testDetails&testNameId=389462240473169692&order=TEST_STATUS_DESC&branch_WF_MainNightlyJobs=__all_branches__&itemsCount=50

I think the problem is the test case only changes network-check-ping6-command to a Windows compatible command, not the network-check-ping-command used with IPv4.

I may also update the network-check-ping6-command to use the default one in Artemis' NetworkHealthCheck class.