OK, once I changed the proper tree cache deployment file, it works. Thanks for
your help!!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968961#3968961
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3968961
___
The cluster-service.xml file does not affect your tree cache in any way.
Completely unrelated. But, changing that one as well was good :-)
The tree cache you're using for the shared data must have a config file as
well. (Unless you're configuring everything programatically, in which case I'd
sa
I read the Wiki page and changed the cluster-service.xml file. After 2 hours,
the tree cache was notified about the loss of a cluster node and it in turn
notified my application. However, 2 hours is much too long. I need to know a
lot sooner. Is there a way to change the timeout value from 2 hou
OK, your problem is the JGroups channel that your cache instance is using isn't
detecting the unplugging of the cable. I bet if you wait about a minute, it
will.
The logging you posted is actually for a completely different channel.
Technically its a different cluster, even though from a surf
Thanks for the quick reply. Regarding the first problem. I see the view change
on node 1 when I Ctrl-C JBoss on node 2. However, I don't see the view change
when I unplug the network cable.
Here is what's logged when I unplug the cable:
10:41:27,090 INFO [dragoneyes] (UpHandler (STATE_TRANSFE
First problem: TreeCacheListener.viewChange(View new_view) passes you a JGroups
View object whenever there is a cluster topology change.
Second problem: No, we have nothing like that.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968724#3968724
Reply to the
