Uploaded image for project: 'ModeShape'
  1. ModeShape
  2. MODE-2618

Restore procedure doesn't work when repository persistence is configured to use DB

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: 5.2.0.Final
    • Component/s: JCR
    • Labels:
      None
    • Release Notes Text:
      This problem is caused by {{createOnStart}} configuration property. Restore procedure suppose repository restart and if this property was set to {{true}} after restore all data will be lost.

      Description

      Repository is configured to use DB persistence (MySQL or Postgres) and dropOnExit property enabled. Repository started with CND and initial content without problems, possible to access loaded nodes. Backup procedure passed without exceptions and problems (it is possible to see backup files in the backup directory). Repository restarted with empty table again and restored from just created backup without problems and exceptions but content is not reachable.

      The behavior is same against each database and test case is running in isolation so the failure is not caused by test case interference.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                oleg.kulikov Oleg Kulikov
                Reporter:
                oleg.kulikov Oleg Kulikov
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: