Success!
I ended up using the multicast IP rather than the port to differentiate the
clusters. The "cluster B" HA-JNDI config in cluster-service.xml looks like this
(note non-default multicast IP):
<!-- Multicast Address and Group used for auto-discovery -->
231.0.0.4
1102
... and then I used these JNDI properties for the client:
java.naming.factory.url.pkgs=jboss.naming:org.jnp.interfaces
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=jnp://the_only_node_in_cluster_B:1100
jnp.discoveryGroup=231.0.0.4
I re-ran my test where I shutdown cluster B, and the client did NOT go find
cluster A, which is precisely the behavior I wanted.
I haven't tried this yet, but I think that I may set
jnp.disableAutodiscovery=true on the client side. The clients are always
configured with the complete list of cluster nodes
(java.naming.provider.url=node1:1100,node2:1100,node3:1100). Disabling
autodiscovery should be easier to manage since I won't need to put a unique IP
or port in the client config (in addition to the list of nodes) for each
cluster.
Thank you very much for your help, bstansberry. I really appreciate it.
-Max
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3910152#3910152
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3910152
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
