[MAGNOLIA-3929] Rendering module cannot be started Created: 28/Dec/11 Updated: 28/Dec/11 Resolved: 28/Dec/11 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 4.5 |
| Fix Version/s: | 4.5 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Daniel Lipp | Assignee: | Daniel Lipp |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 0.25d | ||
| Original Estimate: | Not Specified | ||
| 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 trying to start ee-webapp from current trunk I get: ERROR info.magnolia.module.ModuleManagerImpl : Can't start module rendering |
| Comments |
| Comment by Daniel Lipp [ 28/Dec/11 ] |
|
Looks like this is due to a known jdk bug that is not fixed. We'll have to work around it. |
| Comment by Daniel Lipp [ 28/Dec/11 ] |
|
It looks like this has only been a temporary, local thing on my machine. I could reproduce the error when accessing m-m-commenting from local mvn-repo and from die. After wiping the corrupt jar from mvn-repo and rebuilding whole workspace the problem cannot be reproduced any longer. |