[MAGNOLIA-3322] Installation of tomcat bundle fails with Java heap space exception Created: 13/Oct/10  Updated: 01/Dec/10  Resolved: 18/Nov/10

Status: Closed
Project: Magnolia
Component/s: updatemechanism
Affects Version/s: 4.3.7
Fix Version/s: 4.4

Type: Bug Priority: Critical
Reporter: Andreas Weder Assignee: Magnolia International
Resolution: Not an issue Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Mac OS X 10.6, built-in Java version 1.6.0_20


Attachments: PNG File Bildschirmfoto 2010-10-13 um 16.54.50.png    
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   

I downloaded the official EE bundle containing Tomcat and Magnolia 4.3.7, unpacked it and started the server. The installer fails, because it runs out of heap space.

I suggest to increase the default max memory limit in the Tomcat startup scripts. We leave a bad first impression here.



 Comments   
Comment by Philipp Bärfuss [ 14/Oct/10 ]

Might make sense but there is actually a magnolia_control.sh script which should be used and which sets the memory and the headless flag.

Comment by Felix Rabe [ 14/Oct/10 ]

I've tried to run Magnolia using startup.sh myself just also about a week ago. The place to document this should be the README.txt file of the bundle, in my opinion. People should not have to open a browser to find out how to run the bundle.

Suggestions:

  • Maybe put magnolia_control next to README.txt.
  • Either document how to run in README.txt or create a file QUICKSTART.txt with some basic instructions, pointing to the website for more detailed information.
  • Rename startup and shutdown scripts to something more alerting, like startup/shutdown_internally or startup/shutdown_do_not_run_directly.
Comment by Philipp Bärfuss [ 14/Oct/10 ]

True, a minimal version of the startup instructions should be inlined in the README.txt.

Comment by Magnolia International [ 18/Nov/10 ]

This is "fixed" with MAGNOLIA-3388; a regular ./startup.sh will now also pick up our custom env settings.

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