[MGNLDAM-499] Dam app not starting after a migration from 5.2.x to 5.3.x Created: 08/Aug/14 Updated: 08/Aug/14 Resolved: 08/Aug/14 |
|
| Status: | Closed |
| Project: | Magnolia DAM Module |
| Component/s: | DAM App |
| Affects Version/s: | 2.0.2 |
| Fix Version/s: | 2.0.2 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Eric Hechinger | Assignee: | Eric Hechinger |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Description |
|
When migrating from M5.2.x to M5.3.x, the ContentAppMigrationTask does not run. 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 |