[
http://jira.magnolia.info/browse/MAGNOLIA-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17628#action_17628
]
Jan Haderka commented on MAGNOLIA-2342:
---------------------------------------
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?
> OutOfMemory errors
> ------------------
>
> Key: MAGNOLIA-2342
> URL: http://jira.magnolia.info/browse/MAGNOLIA-2342
> Project: Magnolia
> Issue Type: Bug
> Affects Versions: 3.6.1
> Environment: Java JDK 1.5
> Linux SUSE 9
> Tomcat 5.5.25
> Reporter: Jon Larson
> Assignee: Boris Kraft
> Priority: Critical
>
> 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";
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
