Messaging setup in a network with multiple clusters

[frankthetank]

Hello all,

I have a setup with multiple clusters with unique partition names in one network.

I am using Jboss 4.2.3 and messaging 1.4

The problem is, that while the cluster system can tell who belongs to what group, via the partition name, the JBM cannot.

Ideally I think the messaging system should be able to keep them apart.
We do set the -Djboss.messaging.groupname=$PARTITION_NAME but that does not seem to be enough.

One (imho suboptimal) solution is to change the messaging channel addresses to unique scopes for each cluster.
But that is just avoiding the issue instead of resolving it.
Plus it would mean different scopes for each cluster (if each workplace has their own mini-cluster of one node, then you can image the headache)

I welcome any help that can be provided.

Thanks

[gaohoward]

Hi

You can define the following system properties:

jboss.messaging.datachanneludpaddress
jboss.messaging.datachanneludpport

jboss.messaging.controlchanneludpaddress
jboss.messaging.controlchanneludpport

[frankthetank]

Thanks for the info ... and I had feared that.

I did find a doc stating something similar (http://www.jboss.org/community/wiki/TwoClustersontheSameNetwork) and to be honest, am kinda sad that it will cause problems without these changes.
Not that I cannot work around them, it would have been perfect (even if there are downsides) if it ran out of the box without these changes.

Oh well, guess there is nothing we can do.

thanks again.