This content has been marked as final.
Show 3 replies
-
1. Re: Tree Cache replecation seems to have some problems
prese Aug 20, 2004 7:35 AM (in response to prese)Hi Guys,
I looked to the code of TreeCache and I resolved some how the problem.
I hope that someone can explain me the reason of the implementation.
In startService when the JChannel is initialized the property AUTO_RECONNECT is not set to true.
Due to this when a cache node is plug-in the viewChange is called only on that node and contains as member only that node. Setting the property on true made the following behaviour: a new view address is assigned to that node and all the cluster nodes are notified that a new node appeared.
Can some one tell me if there are some good reasons to not set this property?
Regards
Sebi -
2. Re: Tree Cache replecation seems to have some problems
belaban Aug 20, 2004 8:24 AM (in response to prese)"prese" wrote:
Hi Guys,
I looked to the code of TreeCache and I resolved some how the problem.
I hope that someone can explain me the reason of the implementation.
In startService when the JChannel is initialized the property AUTO_RECONNECT is not set to true.
Due to this when a cache node is plug-in the viewChange is called only on that node and contains as member only that node. Setting the property on true made the following behaviour: a new view address is assigned to that node and all the cluster nodes are notified that a new node appeared.
Can some one tell me if there are some good reasons to not set this property?
Regards
Sebi
This is odd; where did you find it (3.2.5) ? Because in CVS head, AUTO_RECONNECT is set to true in ClusterPartition.createService() by default.
Bela -
3. Re: Tree Cache replecation seems to have some problems
prese Aug 20, 2004 9:10 AM (in response to prese)Hi Bela,
I´m using a 3.2.5 version.
Thanks
Sebi