I've also had the same issue and the suggestion works for me. However, I'm trying to understand what the option "-b 0.0.0.0" is doing. According to the Post-installation documentation(http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.2.2/html/SOA_Getting_Started_Guide/SOA_Getting_Started_Guide-Post_Installation_Testing_and_Starting.html), in section 2.3 it seems that providing a service-binding.xml would allow for connections from other hosts than localhost.
How does providing the -b 0.0.0.0 option affect the use of the service-binding.xml?
The binding service brings all of the port definitions into a single file (without it, they ports are scattered all over the place). This makes it easier to define multiple sets of port configurations if you plan on running multiple instances of the app server on the same host - two instances cannot use the same ports because you get port conflicts.
Alternately, if you have multiple IP addresses defined on you host (either with multiple network cards or youi have set up virtual IP addresses on a single card), you can run multiple app server instance by binding each ot its own IP address. Example:
run -c config1 -b 192.168.0.100
run -c config2 -b 192.168.0.101
Thus, either option (binding to separate IP addresses, or using the binding service) can be used to run multiple instances.
The -b 0.0.0.0 option binds the ports to all IP addresses defined on the host. Thus is you have multiple IP addresses, port 8080, for example, is bound to every address. This means that a browser can access web apps via any of those IP addresses (example, via both http://192.168.0.100:8080 and via http://192.168.0.100:8080, and it will be the exact same web app)
Of course, you can combine the two mechanism. Thus you could use the binding service to define the ports and still use the -b option to bind to one or all IP addresses.