Jan Haderka ha scritto:
There's one JackRabbit issue which might be related:
https://issues.apache.org/jira/browse/JCR-1879
STARTING FROM
Three environemts, PROD, DEV, TEST, PROD has 2 public instances, others
only one.
Our goal: to clone PROD env over TEST and DEV envs.
So:
1) PROD - Bk of mysql db, author and 2 public
2) PROD - Bk of webapp folders
3) DEV - Restore of mysql db, author and public
... restore of the db on different instance of mysql or at least under
different user in same server i presume?
Each magnolia instance has its own db server (mySql) on the same unix
server.
So, we dump the productive magnoliaInstance db (PUBLIC) and restore over
the dev / test magnoliaInstance db (PUBLIC, of course).
DB is everytime jdbc:mysql://localhost:3306/magnoliaPublic (over public
instances) and jdbc:mysql://localhost:3306/magnoliaAuthor (over author
instances).
4) DEV - Delete original webapp folder, drop the PROD webapp folder
(public-01)
just curious: once you have dropped PROD webapp folder in your dev
instance, did you go over
all /repositories/magnolia/workspaces/*/workspace.xml files and updated
the to point to your restored dev database or are they still pointing to
production?
I think we don't need it, because as I said just before, each magnolia
instance has its own db schema "magnoliaPublic" for public instances and
"magnoliaAuthor" for author instances.
The db host is localhost, everytime.
If I can add one clue, when starting each cloned instances, it takes a
lot of time (I mean more than 20 minutes), surely because it rebuilds
indexes. But after this delay, the "LockFactory" exception came out.
Really, no idea...
Many thanks for your help, Jan :-)
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
