Uploaded image for project: 'Magnolia DAM Module'
  1. Magnolia DAM Module
  2. MGNLDAM-14

DMSToDAM migration sometimes fails

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 1.0
    • 1.0
    • None
    • None

    Description

      The bad thing about this bug is, that it's only happening on rare occasions so it's not really reproducible. It already happend when the affected task was created but we thought we could work around it by using ContentUtil.changeNodeType() instead of Node.setPrimaryType(). As this did not really fix the problem, we should now analyze in detail and get rid of it.

      Stacktrace:
      [INFO] [talledLocalContainer] info.magnolia.module.delta.TaskExecutionException: Could not convert contentnodes to DAM format. /demo-project/img/bk/Opener/v-light-3: mandatory child node

      {http://www.jcp.org/jcr/1.0}

      content does not exist
      [INFO] [talledLocalContainer] at info.magnolia.dam.setup.MigrateContentFromDMSToDAMTask.convertContentNodesToDAM(MigrateContentFromDMSToDAMTask.java:183)
      [INFO] [talledLocalContainer] at info.magnolia.dam.setup.MigrateContentFromDMSToDAMTask.doExecute(MigrateContentFromDMSToDAMTask.java:74)
      [INFO] [talledLocalContainer] at info.magnolia.module.delta.AbstractRepositoryTask.execute(AbstractRepositoryTask.java:60)

      No idea why that enforced child node is sometimes not around.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                ehechinger Eric Hechinger
                dlipp Daniel Lipp
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Bug DoR
                    Task DoD