autodiscovery and bind address

[dfisher]

I'm using Jboss 3.2.5 and trying to get all the services to bind to a specific IP address.
I've noticed that autodiscovery is using port 1102 and jgroups is using port 45566.
These services always bind to *.
For autodiscovery I have set the BindAddress attribute, and for JGroups I have set the bind_addr in the UDP tag.
Neither of these seem to have any effect.
I have also tried starting jboss with the -b and --host flags.
Has anyone else had this problem?
Thanks.

[belaban]

In JBoss 3.2.6, the -Dbind.address=1.2.3.4 property helps setting the correct NIC in JGroups, you don't need bind_addr anymore (it is overridden).
In 3.2.5 you still have to use bind_addr in the UDP clause.

Bela

[dfisher]

I've been testing 3.2.6 and setting -Dbind.address does not seem to have any effect.
I still see the following from netstat:
udp4 0 0 *.1102 *.*
udp4 0 0 *.45566 *.*

Can anyone post some info on getting autodiscovery and jgroups to bind to a specific IP?
Thanks.

[sheckler]

Moving from 3.2.5 to 3.2.6 I found the same problem

In JBoss 3.2.6, the -Dbind.address=1.2.3.4 property helps setting the correct NIC in JGroups, you don't need bind_addr anymore (it is overridden).

This doesn't seem to work. With 3.2.6 I did not succeed to bind JGroups to a special IP different from that given with -b flag on JBoss startup as I did with bind_addr running 3.2.5.

Could that be a bug in 3.2.6 or just a missing how to?

Stefan

[belaban]

No, --host (or -b) IPADDR uses the NIC associated with IPADDR, I tested this on 3.2.6 final.

Autodiscovery is a different story, it doesnt use JGroups.
Bela