OK, this is a strange one. I just completed a pretty difficult upgrade of our 
DSpace instance from 1.4.2 to 1.5.2 and everything was working pretty well. I 
guess it still is. You can see the result here:

http://dlynx.rhodes.edu

My big outstanding issue came after I rebooted the server to give it one last 
kick of the tires before calling the whole thing done. After the reboot, 
everything came back up, but the Java process that is the Handle Server (the 
thing that knows to serve up http://dlynx.rhodes.edu/jspui/handle/10267/2423 
when you hit http://hdl.handle.net/10267/2423 to view an object) has stayed at 
100% CPU.

Oddly, during the process of getting the 1.5.2 dspace.cfg correct, I was 
restarting Tomcat and the handle process over and over again, and the handle 
process never did this 100% CPU usage thing. Only after I shutdown the machine 
and cold-started it did this 100% CPU issue appear with the handle process.

Currently, if I kill the process and then restart it using our standard 
/archive/dspace/bin/start-handle-server it will race up to 100% and stay there. 
While the high CPU usage is a concern, it doesn't appear to affect the 
resolution of handles or DSpace or anything else, other than just the 
unnecessary CPU cycle. I can find nothing in any of the logs (handle server, 
tomcat, or DSpace) that would give a clue as to what is going on.

Here is what the handle processes look like with the ps command:

[...@dam ~]$ ps -ef | grep handle
dam       3669     1  0 17:25 ?        00:00:00 /bin/sh 
/archive/dspace/bin/dsru                                   n 
-Ddspace.log.init.disable=true -Dlog4j.configuration=log4j-handle-plugin.prope  
                                 rties net.handle.server.Main 
/archive/dspace/handle-server
dam       3679  3669 99 17:25 ?        00:07:20 java -Xmx512M -Xms64M 
-Dfile.enc                                   oding=UTF-8 -classpath 
:/archive/dspace/lib/activation-1.1.jar:/archive/dspace/l                       
            
ib/bcmail-jdk14-136.jar:/archive/dspace/lib/bcprov-jdk14-136.jar:/archive/dspace
                                   
/lib/commons-cli-1.0.jar:/archive/dspace/lib/commons-codec-1.3.jar:/archive/dspa
                                   
ce/lib/commons-collections-3.2.jar:/archive/dspace/lib/commons-dbcp-1.2.2.jar:/a
                                   
rchive/dspace/lib/commons-fileupload-1.2.1.jar:/archive/dspace/lib/commons-io-1.
                                   
4.jar:/archive/dspace/lib/commons-lang-2.2.jar:/archive/dspace/lib/commons-loggi
                                   
ng-1.0.jar:/archive/dspace/lib/commons-pool-1.4.jar:/archive/dspace/lib/dom4j-1.
                                   
6.1.jar:/archive/dspace/lib/dspace-api-1.5.2.jar:/archive/dspace/lib/dspace-api-
                                   
lang-1.5.2.1.jar:/archive/dspace/lib/fontbox-0.1.0.jar:/archive/dspace/lib/handl
                                   
e-5.3.4.jar:/archive/dspace/lib/icu4j-3.4.4.jar:/archive/dspace/lib/jargon-1.4.2
                                   
5.jar:/archive/dspace/lib/jaxen-1.1.jar:/archive/dspace/lib/jdom-1.0.jar:/archiv
                                   
e/dspace/lib/jempbox-0.2.0.jar:/archive/dspace/lib/log4j-1.2.14.jar:/archive/dsp
                                   
ace/lib/lucene-analyzers-2.3.0.jar:/archive/dspace/lib/lucene-core-2.3.0.jar:/ar
                                   
chive/dspace/lib/mail-1.4.jar:/archive/dspace/lib/mets-1.5.2.jar:/archive/dspace
                                   
/lib/oro-2.0.8.jar:/archive/dspace/lib/pdfbox-0.7.3.jar:/archive/dspace/lib/poi-
                                   
2.5.1-final-20040804.jar:/archive/dspace/lib/postgresql-8.1-408.jdbc3.jar:/archi
                                   
ve/dspace/lib/rome-0.8.jar:/archive/dspace/lib/tm-extractors-0.4.jar:/archive/ds
                                   
pace/lib/xalan-2.7.0.jar:/archive/dspace/lib/xercesImpl-2.8.1.jar:/archive/dspac
                                   
e/lib/xml-apis-1.3.02.jar:/archive/dspace/lib/xmlParserAPIs-2.0.2.jar:/archive/d
                                   space/config -Ddspace.log.init.disable=true 
-Dlog4j.configuration=log4j-handle-p                                   
lugin.properties net.handle.server.Main /archive/dspace/handle-server
dam       4682  4647  0 17:33 pts/1    00:00:00 grep handle
[...@dam ~]$

I think we are running version 6.2.5_02 of the handle server.

Has anyone ever seen anything like this? Any clues as for what could be causing 
it or how to fix it?

BTW, are others occasionally getting a "dspace.org This site is down for 
maintenance. Please check back again soon" message when going to 
http://www.dspace.org ? The wiki appears to be up and fine, but the main 
website gives this message quite a bit, at least today and yesterday.

--
Stacy Pennington
Rhodes College
penning...@rhodes.edu
(901) 843-3968



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to