"This was happening with the old version of JBoss" - Means Windows NLB used to work with JBoss 4.0.3.
I don't know any reason why if this worked before it shouldn't still work with 4.2.3. By default 4.2.3 binds sockets to localhost if you don't pass a -b value to run.bat. But you say you can access the node via http://22.214.171.124:8080 so that doesn't sound like the problem.
Yes, I started JBoss with -b option. ie,
run -b 126.96.36.199
run -b 188.8.131.52
Is there any specific changes to be made in any of the XML files to specify the NLB IP address?
Other diffrence I noticed between JBoss 4.0.3 and 4.2.3 is, when I start 4.0.3 with the command 'run', it binds to localhost as well as the machine IP/Hostname. But this does not happen with 4.2.3. Any specific reason for this change?
4.0.3 would bind to all interfaces, localhost included, if you didn't use -b. Binding to all interfaces by default wasn't secure.
run -b 0.0.0.0
which will bind to all interfaces. If you are using the "all" config that could lead to issues though, which we can get into if the above helps.
I don't use Windows NLB so I can't comment on config details, beyond saying there's nothing in the AS configuration specifically oriented toward integrating with it.
Thanks Brian. It worked !!!!
But, as you mentioned, I'm running my servers on "all" configuration. I will test this out and let you know the results.
Is there any configuration changes that you suggest to run in all configuration?
Good; glad you are making progress.
If you are running with the all config, use this:
run -c all -b 0.0.0.0 -Djgroups.bind_addr=184.108.40.206 (or 220.127.116.11)
JGroups will ignore 0.0.0.0 and pick an interface; using -Djgroups.bind_addr=18.104.22.168 lets you specify which.
Also, clustering's HAPartition service uses the -b value plus the JNDI port (1099 by default) to make up a unique id for each node. If you use -b 0.0.0.0 (or -b 127.0.0.1) each node will come up w/ the same name -- not unique, which may lead to problems. To work around this you can manually specify the name by editing the cluster-service.xml file, replacing: