Bad default TCPPING with TCP mode configuration for clustering in jgroups-channelfactory-stacks.xml

I choose to switch from UDP to TCP and from MPING to TCPPING for Jboss EAP cluster configuration.

In the file server/all/deploy/cluster/jgroups-channelfactory.sar/META-INF/jgroups-channelfactory-stacks.xml

the default MPING configuration for TCP is :

<stack name="tcp"
...
<TCPPING timeout="3000"
initial_hosts="${jboss.jgroups.tcp.tcpping.initial_hosts:localhost[7600],localhost[7601]}"
port_range="1"
num_initial_members="3"/>
...
</stack>

but this configuration do not work, when I configure it by editing jgroups-channelfactory-stacks.xml
, I have this error :

14:50:02,751 ERROR [TCPPING] failed creating initial list of hosts
java.net.UnknownHostException: ${jboss.jgroups.tcp.tcpping.initial_hosts}:192.168.0.1
...
14:50:02,754 ERROR [AbstractKernelController] Error installing to Start: name=HAPartition state=Create
java.lang.RuntimeException: Failure creating multiplexed Channel
...
Caused by: org.jgroups.ChannelException: unable to setup the protocol stack: the following properties in TCPPING are not recognized:

{num_initial_members=2, timeout=3000}
...
Caused by: java.lang.IllegalArgumentException: the following properties in TCPPING are not recognized: {num_initial_members=2, timeout=3000}

After investigating/searching, I found that the following configuration work :

<stack name="tcp"
...
<TCPPING timeout="3000"
initial_hosts="${jgroups.tcpping.initial_hosts:localhost[7600],localhost[7601]}"
port_range="1"
num_initial_members="3"/>
...
</stack>

There is a problem with initial_hosts :
jboss.jgroups.tcp.tcpping.initial_hosts -> DO NOT WORKS
jgroups.tcpping.initial_hosts -> WORKS

I my case, I use :

<TCPPING timeout="3000"
initial_hosts="${jgroups.tcpping.initial_hosts:163.106.38.166[7600],163.106.38.166[7601]}"
port_range="1"
num_initial_members="2"/>

Now I need to fix 2 following problems in cluster

11:16:59,787 WARN [loggerI18N] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/DefaultJMSProvider, XAException.XAER_RMERR

11:16:59,926 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
11:16:59,930 ERROR [ExceptionUtil] ConnectionFactoryEndpoint[jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory] createFailoverConnectionDelegate [la-ebg8ugeg-1-cfu6ugeg-ze88j8-m421y2j4]
javax.jms.JMSSecurityException: User JBM.SUCKER is NOT authenticated
....
11:16:59,970 ERROR [ClusterConnectionManager] Failed to start connection info
javax.jms.JMSSecurityException: User JBM.SUCKER is NOT authenticated
....

PS : I have opened a ticket to add information about How To configure Cluster in TCP mode with TCPPING in Jboss EAP 5.x documentation :
https://jira.jboss.org/browse/JBPAPP-5126