[ 
http://jira.magnolia.info/browse/MAGNOLIA-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Grégory Joseph updated MAGNOLIA-1998:
-------------------------------------

    Description: 
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)

  was:
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 Jackrabbit 1.3.x
    ** Using *Magnolia 3.5.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)


> 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
>
>
> 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
----------------------------------------------------------------

Reply via email to