I meant that the random selection idea would select the port for a cluster of nodes,
not just a particular node, but it would have to exist at a "cluster" startup level
not a "node" startup level.
If I utilized ${system property name} replacement in the file, and then passed the
same port for a multicast configuration to the VM as a system property for every node
in the cluster, it seems to me it would work. Currently, we are doing that for the
cluster partition name, but you are right, I have include that substitution in several
different places. The port number would be a single substitution in a single file.
Does the cited example in UDP.java easily map to multicast configurations too, so I
could test random or hash-selected cluster multicast port numbers for listeners?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3840560#3840560
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3840560
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
