[MAGNOLIA-6313] Increase Java heap size in startup.sh Created: 21/Jul/15  Updated: 24/Jul/15  Resolved: 24/Jul/15

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

Type: Bug Priority: Major
Reporter: Andreas Weder Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: appears-broken, ux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS X Yosemite 10.10.4, JDK 7 update 76


Issue Links:
duplicate
duplicates MAGNOLIA-6276 Increase default Xmx in bundle Closed
duplicates MGNLEE-396 Increase default Xmx in bundle 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   

We should consider increasing the Java heap size in startup.sh/.bat to avoid OutOfMemory errors during first-time installations. I've downloaded the 5.4 bundle, installed and started the author instance, then started the installation of the public instance. The installation froze, which I diagnosed as a memory problem, though I didn't explicitely get an OutOfMemoryError in the logs.

So, without actually doing anything special, I wasn't able to just download and run the bundle. Instead, I installed and started author, shutdown, started up again, installed and started public, shutdown again, then started the server a second time before I could get going.

This is not a very compelling first-time experience for new customers, especially because most of them won't be able to fix the problem as they don't know the system well enough yet.

In our release notes for 5.4, we actually advice to increase the heap size to users of eebundle might run into Out of Memory errors: https://documentation.magnolia-cms.com/display/DOCS/Release+notes+for+Magnolia+5.4#ReleasenotesforMagnolia5.4-Knownissues



 Comments   
Comment by Jan Haderka [ 23/Jul/15 ]

I wonder what are the specifics of that. Could it be slow laptop that increases chances of issue during installation? I personally never had the issue even when installing both instances together at the same time.
Also the place where we found the issue in 5.4, was bit different and related to generating too many image variants at the same time, which most likely points to memory usage by 12-monkeys lib.

Comment by Magnolia International [ 24/Jul/15 ]

We did this just before the 5.4 release. See linked issues.

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