Uncomment and provide a port value for the secondaryBindPort attribute in deploy/messaging/remoting-bisocket-service.xml. Then open that port in the firewall.
I tried it out yesterday and your suggestion worked just fine, thanks. It also worked for remoting-sslbisocket-service.xml. The only problem I found was that in our configuration we are using clustering and we set the ports for each node in the cluster using -Djboss.service.binding.set=ports-default etc. It seems that the secondaryBindPort is not included in the ports that this port setting system of jboss can handle. So I had to manually edit the secondaryBindPort for each node in the cluster.
I was wondering if you have also seen this and have found a better solution.
No, I don't have a solution for your second issue. Our environment is different (we have one JBoss instance per VM) so we don't configure the ports like you do.