[dimitris]

1) Sure, those are not set with -b. But using -u doesn't have any impact on the port listing.

When it says UDP 0.0.0.0:NNNN LISTEN what does it mean? Is this how a multicast listening address is presented?

For a bound unicast UDP socket (e.g. snmp adapter), I get a normal
UDP 192.168.0.20:1161 *:*

[belaban]

Okay, the 0.0.0.0:45566 (for example) addresses you referred to are IP multicast addresses, and netstat or TcpView doesn't show the bind address, but instead 0.0.0.0 for the class D address (should show 230.1.2.3 instead)...
To check whether the other (JGroups related) ports bind correctly, check in the output:
15:37:31,296 INFO [DefaultPartition] Initializing
15:37:31,359 INFO [STDOUT]
-------------------------------------------------------
GMS: address is 192.168.5.2:4371
-------------------------------------------------------
15:37:33,375 INFO [DefaultPartition] Number of cluster members: 1

Then do a "netstat -na |grep 4371", and you'll see
$ netstat -an |grep 4371
UDP 192.168.5.2:4371 *:*

That it is bound to the right interface (I started JBoss with "./run.sh -b 192.168.5.2 -c all")

[dimitris]

Right, so the only thing left is to find out what's those fixed TCP ports and the random UDP ones are used for, and whether those setting need to be externalized.

[brian.stansberry]

2) I didn't see that we use ${jboss.bind.address} in cluster-service.xml/tc5-cluster-service.xml, we should do this.

JGroups should bind to whatever is passed to -b anyway.

Adding bind_addr=${jboss.bind.address} to the configs would make this more explicit. But, a downside is it will encourage people to think they can change that parameter and always get the result they want. If they set bind_addr AND use -b, they're going to bind to jboss.bind.address, not to whatever the configured with the bind_addr property.

Note for users wanting to know how to get around the above problem. Either:

1) Use JGroups 2.2.8 or higher, use bind_addr=address2 in the protocol stack config and start JBoss with -b address -Dignore.bind.address=true
2) Don't configure bind_addr in the protocol stack config. Start JBoss with -b address1 -Dbind.address=address2 (with the parameters in that order.)

[dimitris]

I still don't understand for every of the 2 jgroups stacks:

a) what is the fixed TCP port used for (e.g. cluster-service.xml 49153), why it binds to 0.0.0.0, and how is configured

b) what is the randomly chosen UDP port shown as bound to 0.0.0.0:nnnn (is this the bind_addr you are talking about? is it a Unicast server socket? If so, should't this bind to the jboss.bind.address?)

As a side note, properties like 'ignore.bind.address' should really have an indication of what subsystem they target, e.g. 'jgroups.ignore.bind.address'