[
http://jira.magnolia.info/browse/MAGNOLIA-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15920#action_15920
]
todd edited comment on MAGNOLIA-1998 at 3/10/08 3:54 AM:
-----------------------------------------------------------------
We have consistently reproduced an OutOfMemory condition (memory usage pattern
similar to attached image) using the Magnolia 3.0.x series.
See attached image:
memory-leak_magnolia-CE-3.0.5_jackrabbit-1.3.1.png
* Memory leak ONLY occured with the CACHE DISABLED.
** Cache is bypassed for any request that has request parameters, including the
search feature provided with the samples.
* We tried all possible combinations of the officially distributed Magnolia CE
3.0.2 / 3.0.3 / 3.0.5 with Jackrabbit 1.0.1 / 1.3.1.
* We tried both the Derby persistence manager and the MsSqlPersistenceManager
--> SQL Server 2005
* We also tried Magnolia EE 3.0.5 with Derby (only)
Unfortunately, we haven't had the opportunity to test against the Magnolia
3.5.x series yet.
Our production setup:
* Windows Server 2003 R2
* Sun JDK 1.5.0 update 14
* JBoss 4.2.2
* Magnolia CE 3.0.5 with Jackrabbit 1.3.1
* SQL Server 2005 (and Derby for local development environments - memory leak
reproducible either way)
* We have some custom filters etc. to integrate our application with Magnolia,
but we used a standard Magnolia install as a control when load testing.
was (Author: todd):
We have consistently reproduced an OutOfMemory condition (memory usage
pattern similar to attached image) using the Magnolia 3.0.x series.
See attached image:
* memory-leak_magnolia-CE-3.0.5_jackrabbit-1.3.1.png
* Memory leak ONLY occured with the CACHE DISABLED.
** Cache is bypassed for any request that has request parameters, including the
search feature provided with the samples.
* We tried all possible combinations of the officially distributed Magnolia CE
3.0.2 / 3.0.3 / 3.0.5 with Jackrabbit 1.0.1 / 1.3.1.
* We tried both the Derby persistence manager and the MsSqlPersistenceManager
--> SQL Server 2005
* We also tried Magnolia EE 3.0.5 with Derby (only)
Unfortunately, we haven't had the opportunity to test against the Magnolia
3.5.x series yet.
Our production setup:
* Windows Server 2003 R2
* Sun JDK 1.5.0 update 14
* JBoss 4.2.2
* Magnolia CE 3.0.5 with Jackrabbit 1.3.1
* SQL Server 2005 (and Derby for local development environments - memory leak
reproducible either way)
* We have some custom filters etc. to integrate our application with Magnolia,
but we used a standard Magnolia install as a control when load testing.
> 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: 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)
> * 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/docs/en/editor/stayupdated.html
----------------------------------------------------------------
