Re: [Dspace-devel] [Dspace-tech] HTTP Status 500 error

2011-04-18 Thread Mark H. Wood
It looks to me like it's running very low on memory.  The message
seems to mean that the JRE is spending too much time
garbage-collecting.  You might want to install a resource monitor in
your servlet container and watch how memory management is behaving --
I use LambdaProbe but there are others.

-- 
Mark H. Wood, Lead System Programmer   mw...@iupui.edu
Asking whether markets are efficient is like asking whether people are smart.


pgpjiPQbNOPmC.pgp
Description: PGP signature
--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel


Re: [Dspace-devel] [Dspace-tech] HTTP Status 500 error

2011-04-18 Thread Peter Dietz
Since it looks like your system is low on memory, it could be due to an
increase in traffic, a memory leak (which something like LambdaProbe could
help you detect), a misconfiguration, or just overall memory usage and
exhaustion. If there are spare resources on the server, you could try to
increase the amount of memory dedicated to tomcat/java through java_opts or
tomcat configuration. You could also try to bump up the amount of memory
allocated to the server, either physically adding memory chips, or upping
the allocation to the virtual machine. Also, another option would be to
disabled unused features that may be consuming memory. If you only use jspui
and solr, then you could configure tomcat to not deploy xmlui, lni, sword,
oai, etc.

Also, another note is that JSPUI consumes less memory than xmlui. I'm not
sure which ui you're running.

The advice I've given is more-or-less tips on what to do when you're low on
memory, but aren't specific to the problem/exception of errors during
garbage collection. If you're using 1.6.0 or 1.6.1, you could be running
into solr problems, which are usually manifested in a different error, but
you can always take a look at some of the solr performance fixes:
http://atmire.com/statistics_performance.php

Peter Dietz



On Mon, Apr 18, 2011 at 3:00 PM, Mark H. Wood mw...@iupui.edu wrote:

 It looks to me like it's running very low on memory.  The message
 seems to mean that the JRE is spending too much time
 garbage-collecting.  You might want to install a resource monitor in
 your servlet container and watch how memory management is behaving --
 I use LambdaProbe but there are others.

 --
 Mark H. Wood, Lead System Programmer   mw...@iupui.edu
 Asking whether markets are efficient is like asking whether people are
 smart.


 --
 Benefiting from Server Virtualization: Beyond Initial Workload
 Consolidation -- Increasing the use of server virtualization is a top
 priority.Virtualization can reduce costs, simplify management, and improve
 application availability and disaster protection. Learn more about boosting
 the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
 ___
 Dspace-devel mailing list
 Dspace-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-devel


--
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel