JGRP000032 is logged when multiple JBoss EAP Pods are started at once

Issue

When configuring a JBoss EAP 7.4 cluster using DNS_PING, starting multiple Pods at once may result in logs such as JGRP000032, or a UUID is included in the ISPN000094 message instead of the pod name:

03:21:57,613 WARN  [org.jgroups.protocols.TCP] (FD_SOCK pinger-18,ee,helloworld-4-6mg9c) JGRP000032: helloworld-4-6mg9c: no physical address for e6945d8f-05f8-4ee6-80c2-c2b90d83a4cb, dropping message
...
03:22:00,021 INFO  [org.infinispan.CLUSTER] (ServerService Thread Pool -- 77) ISPN000094: Received new cluster view for channel ee: [helloworld-4-7bq6k|9] (10) [helloworld-4-7bq6k, 8e0ec55f-4d11-4084-9174-88658d8b7bac, helloworld-4-sf9vc, helloworld-4-495zw, helloworld-4-6mg9c, helloworld-4-kpstr, helloworld-4-fzzr6, helloworld-4-rt6xd, helloworld-4-g8tcr, helloworld-4-bsswd]