Steve: I am not sure if this is your problem, but I found at our site that we usually have a problem like this if we are being hammered by harvesters. It seems to me that multiple harvesting of DSpace content can trigger a runaway java process (I could be wrong, but that’s my theory). Do you have a robots.txt file set up? Also, do you have a sitemap set up? Either of these can help, but won’t totally fix the problem. Another thing might be to adjust the java opts in your tomcat. I don’t know how much memory to have to play around with, but I am using: JAVA_OPTS="-server -Xms1024m -Xmx2048m -Xmn64m -Dfile.encoding=UTF-8 -XX:+UseParallelGC -verbose:gc -Xloggc:/dspace/dspace/log/gc.log -XX:+HeapDumpOnOutOfMemoryError -XX:PermSize=1024m -XX:MaxPermSize=1024m -XX:-UseGCOverheadLimit"
These days I am restarting tomcat once a week (usually on Friday evenings) to fix our java heap problems. I know some other DSpace users restart their tomcat every day. By the way, I am running DSpace 1.8.2 using Tomcat 7. George Kozak Digital Library Specialist Cornell University Library Information Technologies (CUL-IT) 218 Olin Library Cornell University Ithaca, NY 14853 607-255-8924 From: Steve Thomas [mailto:[email protected]] Sent: Wednesday, April 02, 2014 9:25 PM To: [email protected] Subject: [Dspace-tech] DSpace becomes unresponsive, and I'm out of ideas We're having continuing performance problems with our DSpace server. We're running version 1.6.2 on RHEL 4, so, yeah, everything is old. But service has been reliable, mostly, until recently. The symptom is that DSpace will become "unresponsive" at the browser. Checking the server, we'll typically find that the java process is running at 170% cpu, so my guess is a runaway process, which explains the slow/no response. But why? Checking the logs, both dspace.log and catalina.out, gives no real clue. dspace.log is typically full of broken pipe errors, but these are,I guess, another symptom. We also get broken pipe errors through the day, even when DSpace is running normally. Possibly unrelated, we also periodically find that dspace.log has filled up all available disk space -- more than 100GB! With a file that large, it's difficult to scroll through, but I've not found any obvious answers there. So I'm out of ideas here as to where to even look for cause. (And yes, I've already had the upgrade idea. Not currently an option I'm afraid.) Can anyone help with suggestions? Stephen Thomas Library Systems Manager Barr Smith Library UNIVERSITY OF ADELAIDE SA 5005 AUSTRALIA Phone: +61 8 831 35190 / Mobile: 0402 069 087 / Fax: +61 8 831 34369 Email: [email protected]<mailto:[email protected]> CRICOS Provider Number 00123M Please consider the environment before printing. IMPORTANT: This message may contain confidential or legally privileged information. If you think it was sent to you by mistake, please delete all copies and advise the sender. For the purposes of the SPAM Act 2003, this email is authorised by The University of Adelaide.
------------------------------------------------------------------------------
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
