You can see who the members of a cluster are by looking at the
jboss:service=DefaultPartition mbean in jmx-console. Except, replace
"DefaultPartition" with whatever you set with -g.
Re: your JMS issue, I'm guessing someone is looking up a ConnectionFactory from
the wrong cluster; i.e. a config
BTW this test was performed on Windows Server 2003.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138150#4138150
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138150
___
jb
I have setup the clusters and I am passing -c, -b, -g and -u parameters (with
unique values for the clusters) in the run script. I am using JMS to send
message from one cluster to another and it is picked up by the third cluster
also. I am using a JMS bridge for that and assuming (I think that i
If you look at the jboss-service.xml mbean where you set ports-01, etc, there's
a "StoreURL" attribute:
|
| ports-01
| ${jboss.home.url}/docs/examples/binding-manager/sample-bindings.xml
|
|org.jboss.services.binding.XMLServicesStoreFactory
|
|
T
Thanks for that info, Brian.
Is there any resource online that can provide info on what settings in which
files (e.g. cluster-service.xml, hajndi-jms-ds.xml etc.) are being overridden
when one specifies port setting (ports-default, ports-01 etc.) in
jboss-service.xml. There seems to be ports
No, it is not. The JGroups channels in nodes meant to be part of different
clusters will be listening on the same multicast addresses and ports and will
thus see each others traffic. The use of -Djboss.partition.name will prevent
that traffic from getting out the JGroups channel, but you still
