By default, JBoss AS has defined multicast UDP ports through which the ongoing intra-cluster communication, and those defined in file jbossas/server/all/deploy/cluster/jgroups-channelfactory.sar/META-INF/jgroups-channelfactory-stacks.xml. This file contains a number of protocol stack configurations used by the AS's JGroups ChannelFactory. In the firewall enviroment you must open these ports between all nodes

<UDP
     singleton_name="shared-udp"
     mcast_port="${jboss.jgroups.udp.mcast_port:45688}"
     mcast_addr="${jboss.partition.udpGroup:228.11.11.11}"

.....

<stack name="jbm-data"
        description="Stack optimized for the JBoss Messaging Data Channel">
    <config>
        <TCP singleton_name="jbm-data"
            start_port="${jboss.messaging.datachanneltcpport:7900}" - for JMS

....

<MPING timeout="5000"
   mcast_addr="${jboss.partition.udpGroup:228.6.6.6}"
  mcast_port="${jboss.messaging.datachanneludpport:45710}" - UDP multicast

and yet to be add element bind_port (the port to which the unicast receive socket) must be configured to concrete value because the default value is random and servers are behind the firewall.

        <!--  UDP transport config meant to be shared between different channels
               with different requirements. Message bundling is disabled in this
               general-purpose config as it can add latency to synchronous RPCs. -->
         <UDP
              singleton_name="shared-udp"
              mcast_port="${jboss.jgroups.udp.mcast_port:45688}"
              mcast_addr="${jboss.partition.udpGroup:228.11.11.11}     "

         bind_port="44401" - example - but to next node add element bind_port with diferent value for example :44402