[
https://jira.duraspace.org/browse/DSCR-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21018#action_21018
]
Mark Diggory commented on DSCR-24:
----------------------------------
Could this be caused by running solr through ajp proxy? What is your url for
connecting to solr?
> memory leak in discovery
> ------------------------
>
> Key: DSCR-24
> URL: https://jira.duraspace.org/browse/DSCR-24
> Project: DSpace Discovery Module
> Issue Type: Bug
> Reporter: james bardin
> Priority: Major
>
> I've tracked a significant memory leak in a dspace 1.7.1 installation back to
> the discovery module. The JVM heap would balloon to >1G within a couple days
> depending on usage.
> A heap dump showed discovery objects in all the "leak suspects" reports
> (SimpleSearch, RelatedItems).
> Disabling discovery leveled off the memory use (and as a bonus, brought down
> the latency of the xmlui significantly).
> jdk 1.6.0_24
> Tomcat 7.0.16
> Apache 2.2 proxy using ajp
> I don't have the resources to debug this, but I have a 360MB heap dump I can
> post if someone wants it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
