[MAGNOLIA-3973] bootstrap: can't overwrite top level nodes when running jackrabbit 2.2.11 Created: 20/Feb/12 Updated: 29/Nov/12 Resolved: 20/Feb/12 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | None |
| Fix Version/s: | 4.5 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Philipp Bärfuss | Assignee: | Philipp Bärfuss |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| 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
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Description |
|
The original problem is explained here: JCR-3239: Removal of a top level node doesn't update the hierarchy manager's cache. For the moment we have to workaround the issue in the BootstrapUtil. |
| Comments |
| Comment by Joerg von Frantzius [ 09/Nov/12 ] |
|
I'm seeing this issue with Magnolia 4.5.6 when trying to bootstrap a top-level node: 12-11-09 14:25:10 WARN PUBLIC[main]info.magnolia.importexport.BootstrapUtil: Deleted already existing node for bootstrapping: /sectionBookmarksActivator 12-11-09 14:25:10 ERROR PUBLIC[main]info.magnolia.module.InstallContextImpl: > Error while installing or updating contentpool-module module. Task 'Bootstrap' failed. (ItemExistsException: a node with uuid fd46542c-a427-46f9-a0b0-0c5c259f96fb already exists!) It seems the workaround got rolled-back here:
I guess this issue should be reopened if the workaround got reverted? By the way, when I issued a hm.save() between deletion and invocation of DataTransporter.importXmlStream() then it worked. Maybe that could be a workaround? I have no clue, though, where hm.save() is invoked normally during or after bootstrapping, and whether this would mean a change of behaviour. |
| Comment by Jan Haderka [ 29/Nov/12 ] |
|
Hi Jorg, please see related issue - The workaround was rolled back because it was causing other issues during upgrades. It never really worked. Regards, |
| Comment by Joerg von Frantzius [ 29/Nov/12 ] |
|
Thanks Jan. Since Ultimately, of course someone will need to fix JCR-3239 ... |