[MAGNOLIA-1683] mgnl-files are not extracted on subsequent nodes when using jackrabbit clustered instances Created: 16/Aug/07  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: zam6ak Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnilia 3.1-SNAPSHOT
Jackrabbit 1.3.1
JBoss 4.0.5GA (Tomcat 5.5.20)
Java 6.02


Issue Links:
relation
is related to MAGNOLIA-2697 Allow for installation on partially c... Closed
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   

When configuring multiple public instances using Jackrabbit clustering mgnl-files are not being extracted onto the filesystem for other nodes in the cluster...
Following folders are missing content on subsequent nodes in cluster:

/templates
/docroot

Workaround:

  • take /templates and /docroot and copy it over other instance WARs

Possible implication:

  • impact on update mechanism


 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:29:18 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.