You always need the Jackrabbit cluster setup, since Jackrabbit needs to know the order of events and maintains a few node caches. The persistence manager (eg. storing in a DB) is a relative simple storing solution without knowledge of the higher-level JCR actions taking place. With clustering configured, it should work in your setup, if the replication between the Oracle DBs is immediate.
Regards, Alex On Wed, Jul 16, 2008 at 2:09 AM, Pascal_b <[EMAIL PROTECTED]> wrote: > What if they do not share the same persistent DB (I'm working on a High > Availability system where the content need to be available 24X7). > > The setup I have is 2 oracle databases with replication enabled and 2 > jackrabbit instances running on different servers. Each jackrabbit instance > connects to a different database. Only one jackrabbit instance is used for > write(webdav). The data gets replicated correctly on the other side but I > have to restart the second jackrabbit instance to be able to access the new > content. > > Any hint on what can be done in this case ? > > Thanks > > Pascal > > > > Alexander Klimetschek wrote: >> >> If they share the same persisted data (ie. tables in this case), you >> need to set up a journal for clustering jackrabbit. See >> http://wiki.apache.org/jackrabbit/Clustering and search the mailing >> list - there were many recent discussions about clustering. >> >> Regards, >> Alex >> >> On Fri, Jul 4, 2008 at 12:00 AM, MARTINEZ Antonio >> <[EMAIL PROTECTED]> wrote: >>> Hello, >>> >>> Can we have multiple jackrabbit instances (in different cluster nodes) >>> talking to he same backend DB (mysql in my case) ? >>> >>> Or does jackrabbit keep some local cache that would make this >>> configuration not to work? >>> >>> >>> Thanks, >>> Antonio >>> >> >> >> >> -- >> Alexander Klimetschek >> [EMAIL PROTECTED] >> >> > > -- > View this message in context: > http://www.nabble.com/Multiple-Jackrabit-instances-tp18269071p18477574.html > Sent from the Jackrabbit - Users mailing list archive at Nabble.com. > > -- Alexander Klimetschek [EMAIL PROTECTED]
