Juan Diego B.
> Date: Tue, 8 Jun 2010 13:18:10 -0400
> From: justinedel...@gmail.com
> To: users@jackrabbit.apache.org
> Subject: Re: Problems Migrating Cluster Data
>
> A few things jump out in the configuration below:
> 1) You aren't assigning a Cluster ID. This is r
space, Versioning)
? Thanks in advance.
Regards,
Juan Diego Botiva
> Date: Tue, 8 Jun 2010 13:18:10 -0400
> From: justinedel...@gmail.com
> To: users@jackrabbit.apache.org
> Subject: Re: Problems Migrating Cluster Data
>
> A few things jump out in the configuration below:
> 1) You
;
>
>
>
>
>
>
> value="jdbc:mysql://192.168.1.144:3306/dbrep?autoReconnect=true"/>
>
>
>
>
>
>
>
> Date: Mon, 7 Jun 2010 14:04:31 +0200
> Subject: Re: Problems Migratin
Hi,
I think the main problem is that each cluster node uses it's own
persistence manager (database on localhost). See
http://wiki.apache.org/jackrabbit/Clustering "That means all
Jackrabbit cluster nodes need access to the SAME persistent storage
(persistence manager and data store)." By the way,
gt; Date: Mon, 31 May 2010 09:16:05 +0200
> Subject: Re: Problem
Hi,
This sounds like a configuration problem. If you change the
persistence location, please ensure you change the repository.xml as
well as all workspace.xml files.
See also see http://wiki.apache.org/jackrabbit/Clustering
If the problem persists please post the configuration (all
repository.xm
Hi!
We recently moved our production JCR repository to a 2-node jackrabbit cluster
with a MySQL backend, everything went Ok. We need to make some testing with
production data on other server with no cluster configuration but when we
import the MySQL dump into our testing database, the nodes sto
