Hello Eugene > > Hi Folks, > > I'm getting a strange behavior after enabling the jgroups > repo clustering. I see that both nodes "find" each other in > the slide log. > I then setup two tomcat instances (war builds), I add a > document to one node and the second node gets the update. > Subsequent modifications to the repo go unannounced to the > second node.
Hmmm, I think I do not understand the problem...i suppose if you add a document to the first node, this node gets the new document also, right? So, but what is wrong in your opinion that the second node also gets the update? What do you expect from clustering? How it normally works, is that clustered repositories all write to the same database, and the notifications are send around just to invalidate the caches of the other repo instances, such that, on a request, they re-fetch the node from the database. Aren't you confusing clustering with distributed storage? Ard > > I've definitely seen repo clustering working consistently at > one point. > Does this sound like anything obvious or familiar to anyone? > > TIA for any help! > > -- > Eugene Fabrikant > Bluenog Corporation > > bluenogef (Y!IM, AIM) > > > > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > > Searchable archives can be found at: > MarkMail: http://hippocms-dev.markmail.org > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
