[
https://jira.duraspace.org/browse/DS-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bram Luyten (@mire) updated DS-1553:
------------------------------------
Attachment: PSI-Probe-Tomcat-7.0.30.png
PSI-Probe-Tomcat-7.0.40.png
I did the necessary tests with Tomcat 7.0.30. It's definitely solved there. So
the note in the documentation can include that it's recommended to run Tomcat
7.0.30 or higher.
> Huge heap on Tomcat 7.0.29
> --------------------------
>
> Key: DS-1553
> URL: https://jira.duraspace.org/browse/DS-1553
> Project: DSpace
> Issue Type: Documentation
> Reporter: Bram Luyten (@mire)
> Assignee: Bram Luyten (@mire)
> Attachments: 7.0.29-classes.png, 7.0.29-telemetry.png,
> 7.0.40-classes.png, 7.0.40-telemetry.png, PSI-Probe-Tomcat-7.0.30.png,
> PSI-Probe-Tomcat-7.0.40.png
>
>
> When using Tomcat 7.0.29, heap space shoots up to over 600MB when starting up
> DSpace, only deploying the XMLUI exploded war. Even without SOLR.
> Using Tomcat 7.0.40, this is no longer the case and just uses 50MB of heap.
> Right now, I'm not sure whether this is just a local configuration problem,
> or whether there's a serious reason to put a warning in the docs to ensure
> that people don't use 7.0.29.
> Would be great if anybody is able to reproduce/confirm this excessive memory
> usage on tomcat 7.0.29.
> Java opts for 7.0.29 -Xms1024m -Xmx1024m (won't even run without declaring
> more heap space).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
