• That’s correct before 4.2.0.GA jboss always bound to the any address “0.0.0.0″. You wouldn’t believe how many people would put unprotected instances of JBoss on the internet, or even on their own local LAN. Now you have to explicitly choose to do that, so it takes some thinking about before you revert to the old default behaviour with the “-b’ option of jboss. e.g.
./run.sh -b 0.0.0.0

For Windows, use

run.bat -b 0.0.0.0

Note: Starting the server with -b 0.0.0.0 will get things going for you. However, you are strongly advised to secure your JBoss instance, atleast when using the server in production.

Suggestion: It would be extremely helpful to provide a script or something to lock down the admin features. Or just disable them by default. My systems admin perspective: JBoss is some thing that came with the application. I had no idea these admin tools were running and accessible on our public website (running JBoss on port 80). How do I stop them from running?