Without changes you can achieve binding if you add -b 0.0.0.0 to the run.sh parameters if you start the instance.
Thanks for the reply!
That was what I tried before manually updating the jboss-service.xml file. I get the same result. The JNP port listens on 0.0.0.0:1099, but the Invoker still listens on either 127.0.0.1:3873 or on some machines it listens on <specific_ip>:3873
So I'm hoping I"m just missing a config entry somewhere and it's possible to get the Invoker to listen on 0.0.0.0:3873.
Do you have an active ServiceBindingManager activated in the jboss-service.xml. I suppose that can be the reason.
Another option is to try 4.2.3 or later and check whether it happens here.
I will check on the ServiceBindingManager, thanks!
We are in the process of upgrading to JBoss 7, but it is not on the near horizon, though if I can't solve this issue, that will likely change.