[
http://jira.magnolia.info/browse/MAGNOLIA-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16138#action_16138
]
pbracher edited comment on MAGNOLIA-1998 at 5/8/08 2:35 PM:
-------------------------------------------------------------------
OK I wrote a jmeter test plan which does a heavy authoring (three threads):
- create pages
- add 10 paragraphs
- activate every now and then
- activation uses versioning (but no workflow)
The setup I used was:
- tomcat 5.5 (default magnolia bundle)
- external db (h2)
- -Xmx256M
I add the graph of the tenured gen space which shows:
- it increases (slowly but steady)
- after stopping jmeter, the memory is not freed
As a next step I will test 3.6 (to see if the latest changes have an impact on
that)
was (Author: pbracher):
OK I wrote a jmeter test plan which does a heavy authoring (three threads):
- create pages
- add 10 paragraphs
- activate every now and then
- activation uses versioning (but no workflow)
I add the graph of the tenured gen space:
- it increases (slowly but steady)
- after stopping jmeter, the memory is not freed
As a next step I will test 3.6 (to see if the latest changes have an impact on
that)
> Potential memory leak: investigation.
> -------------------------------------
>
> Key: MAGNOLIA-1998
> URL: http://jira.magnolia.info/browse/MAGNOLIA-1998
> Project: Magnolia
> Issue Type: Task
> Reporter: Vivian Steller
> Assignee: Boris Kraft
> Priority: Critical
> Attachments: 3.5.4.png, Mag3.0.5Jackrabbit1.3.3_memGraph.JPG,
> Mag3.5Jackrabbit1.3.3_memGraph.JPG, Mag3.5Jackrabbit1.3.3_memGraph_128M.JPG,
> magnoliaMemLeak_toMag.doc, memory-leak_magnolia-CE-3.0.5_jackrabbit-1.3.1.png
>
>
> Several users have reported memory issues. We're creating this issue to
> collect information, reports and other evidence. Please attach relevant files
> and leave comments on your experiences. Thanks!
> *Current status:*
> * We're investigating about this issue, but we're lacking evidence of a real
> leak in Magnolia 3.5 when used with an external database at the moment. (see
> comments below)
> * Magnolia 3.0 must not be used with jackrabbit 1.3 but with the delivered
> 1.0 version
> * There have been too many architectural changes in 3.5 to backport the fixes
> to the 3.0 branch
> * The following definitely helps:
> ** Using an external database such as MySQL
> ** Using *Magnolia 3.5.x* (and Jackrabbit 1.3.x)
> * If you're experiencing OutOfMemoryError: PermGen space, you need to
> increase the -XX:MaxPermSize JVM setting.
> * If you're still having memory issues after applying the above advices,
> please report them here with the following information:
> ** Operating system:
> ** Java version:
> ** Container (tomcat, jetty, ...) and version:
> ** Precise JVM settings (JAVA_OPTS, CATALINA_OPTS, ...)
> ** How is your container started:
> ** Is there any specific operation that triggers your memory issues?
> ** Any stacktraces or relevant log files (in attachment, with your name
> in the filename, please)
--
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/
----------------------------------------------------------------
