[MAGNOLIA-6420] Magnolia hangs upon fresh installation of the bundle on MacBooks Created: 06/Oct/15  Updated: 26/Oct/15  Resolved: 19/Oct/15

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

Type: Bug Priority: Critical
Reporter: Jan Haderka Assignee: Christoph Meier
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1.75d
Original Estimate: Not Specified
Environment:

AirBook, mid 2011, 4gb ram,
Java 8u60, Magnolia 5.4.2 ee bundle (tar.gz)


Attachments: PNG File Screen Shot 2015-10-06 at 16.54.14.png    
Issue Links:
documentation
to be documented by DOCU-623 Warn that install of Magnolia can fai... Closed
supersession
is superseded by MAGNOLIA-6421 evaluate H2 database and replacement ... Closed
is superseded by MGNLCE-7 Stop the installation if the open-fil... Closed
is superseded by MGNLEE-414 Stop the installation if the open-fil... 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:
Story Points: 5

 Description   

This problem so far occurs only on old airbooks.

To reproduce:

  • Download the bundle (5.4.2, tar.gz in this case)
  • startup the bundle for the first time
  • proceed w/ installation on both author and public instance as close to same time as possible
  • upon finishing the installation click on "startup Magnolia" on both instances (again as close to same time as possible)

result:

  • in one instance, license page loads
  • the other instance just hangs loading the license/registration page
  • upon entering license in first instance and submitting the page, this instance will hang as well
  • memory usage observed is 1GB allocated to JVM
  • CPU usage is similar to idling instance of tomcat/magnolia (2-4%)
  • after 5 minutes, situation is still same, didn't wait any longer


 Comments   
Comment by Philipp Bärfuss [ 06/Oct/15 ]

Yes, this is how I experienced it.

Comment by Philipp Bärfuss [ 19/Oct/15 ]

First we have to document it properly:

  • DOCU-623 Warn that install of Magnolia can fail on MacBooks if the open file limit is not set

Then warnt the user if we can:

And to get the problem solved we should replace Derby if we can

  • MAGNOLIA-6421 evaluate H2 database and replacement derby in the standard bundle
Comment by Christopher Zimmermann [ 20/Oct/15 ]

Another option: Change the install screen to instruct the user to run the web updates in sequence.

Generated at Mon Feb 12 04:14:21 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.