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

Dam app not starting after a migration from 5.2.x to 5.3.x

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • 2.0.2
    • 2.0.2
    • DAM App
    • None

      When migrating from M5.2.x to M5.3.x, the ContentAppMigrationTask does not run.
      The whole contentConnector definition is not created & the workbench definition is not migrated

      Thus DAM App did not start and generate 

      java.lang.NullPointerException
	at java.util.Hashtable.get(Hashtable.java:334)
	at info.magnolia.repository.WorkspaceMapping.getWorkspaceMapping(WorkspaceMapping.java:123)
	at info.magnolia.repository.DefaultRepositoryManager.getSession(DefaultRepositoryManager.java:228)
	at info.magnolia.context.DefaultRepositoryStrategy.internalGetSession(DefaultRepositoryStrategy.java:61)
	at info.magnolia.context.AbstractRepositoryStrategy.getSession(AbstractRepositoryStrategy.java:74)
	at info.magnolia.context.AbstractContext.getJCRSession(AbstractContext.java:132)
	at info.magnolia.context.MgnlContext.getJCRSession(MgnlContext.java:649)

      Also showed in dif report
      http://hudson.magnolia-cms.com/view/Migration/job/int_migration-tests_5.2-to-5.3.x-branch/Diff_Reports/

        Acceptance criteria

          1. Screen Shot 2014-08-08 at 10.39.44.png
            Screen Shot 2014-08-08 at 10.39.44.png
            46 kB

              ehechinger Eric Hechinger
              ehechinger Eric Hechinger
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD