[MAGNOLIA-2342] OutOfMemory errors Created: 28/Aug/08  Updated: 20/Jan/09  Resolved: 02/Sep/08

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

Type: Bug Priority: Critical
Reporter: Jon Larson Assignee: Boris Kraft
Resolution: Workaround exists Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Java JDK 1.5
Linux SUSE 9
Tomcat 5.5.25


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   

Upgrade from 3.0.3 to 3.5.8
Upgrade from 3.5.8 to 2.6.0
Upgrade from 3.6.1

We moved to berkley db
je-3.3.62.jar
magnolia-bdb-1.2.1.jar

JDK
1.5

Java Options
JAVA_OPTS="-Xms128M -Xmx1024M -Djava.awt.headless=true";



 Comments   
Comment by Jan Haderka [ 28/Aug/08 ]

Hi Jon,
could you be more specific? When do you experience OOM issues?

  • Does it happen while executing certain operations (e.g. bootstrapping or importing xml files) or is it moreless random?
  • How long does it take on average before you OOM after restart of Tomcat?
  • Are there any applications other then Magnolia running on your Tomcat?
  • Can you profile the application to find out what is consuming too much memory?
  • It is possible to get OOM with BDB if you have enough content in your application since at runtime it uses same JVM for storing and caching the data. Can you migrate your data to other database like e.g. MySql and see if you still get the OOM errors?
Comment by Jan Haderka [ 02/Sep/08 ]

BDB and Derby are inherently sensitive to memory and usage of memory grows with the size of the database. Switch to backing store that is not running in same JVM (e.g. MySQL) as your Magnolia instance to prevent this kind of problems.

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