Jboss 4.2.0CR only binds to localhost

[risenhoover]

HI All,

I've installed the latest 4.2.0CR build and deployed my application onto a server (neon). I have a mod_jk connector running on a firewall (nitrox) that dispatches connections to the instance running on neon.

The problem is that whereas Jboss 4.0.xCR would bind to all interfaces by default, it appears that 4.2.0CR binds only to localhost.

With 4.2.0 running (and configured out of the box), an nmap of localhost shows it's listening on port 8009, but an nmap of 10.0.0.5 shows it's not listening.

I've tried a number of ways to get the AJP connector to listen on all interfaces but they all seem to fail.

This works, but of course it requires me to hard-code it:


So what happened -- was there a policy decision made where somebody decided that the connector should only listen on localhost by default?

[markusdöring]

http://www.jboss.com/index.html?module=bb&op=viewtopic&t=103312

* JBossAS now binds its services to localhost (127.0.0.1) *by default*, instead of binding to all available interfaces (0.0.0.0). This was primarily done for security reasons because of concerns of users going to production without having secured their servers properly. To bind JBoss services to a particular interface, simply run jboss with the -b option.

[risenhoover]

Thanks for the response.

I ultimately figured out how to work around it but it's good to see I'm not nutty.