I use: http://psi-probe.googlecode.com/ to monitor memory usage.
Still have to get all the bells and whistles going thought.
If anybody knows of a better open source app, please let me know.


On 6 May 2010 19:27, Peter Dietz <dietz...@osu.edu> wrote:

> With the upgrade you essentially have another webapp running, i.e. SOLR,
> which means your instance will need more memory. More for when doing a lot
> of work, and more to be permanently used i.e "permgen". When I've performed
> large batch processing (converting and importing old log files), I've bumped
> up my max memory for tomcat/java and increased the permgen. I'm not sure if
> there is something triggering solr to jump "over the edge" in your case, but
> after I've allocated more memory to java/tomcat, problems just go away.
>
> Thus for me it would be: edit /etc/init.d/tomcat6
> JAVA_OPTS="-Djava.awt.headless=true -Xmx1536M *-XX:MaxPermSize=128m*"
>
> or, however you normally set JAVA_OPTS
>
> Peter Dietz
> Systems Developer/Engineer
> Ohio State University Libraries
>
>
>
>
> On Thu, May 6, 2010 at 11:41 AM, Anderson, Charles W <
> bill.ander...@library.gatech.edu> wrote:
>
>> We're on our second attempt to upgrade from 1.5.2 to 1.6.  We have been
>> plagued with m
>> memory errors both times, and we' think we've narrowed it down to
>> something that's going
>> on in the solr webapp.  We've got solr running in it's very own Tomcat
>> instance; which has
>> helped, but hasn't completely eliminated the problems.
>>
>> Just before we crash, we're seeing lots and lots of the following in the
>> dspace log:
>>
>>    org.apache.solr.common.SolrException: Internal Server Error
>>
>> Then, eventually, we start getting this:
>>
>>    org.apache.commons.dbcp.SQLNestedException: Cannot get a connection,
>> pool error: Timeout waiting for idle object
>>
>> Meanwhile, over in catalina.out, we have these, which seem to correspond
>> to the solr errors in the dspace log:
>>
>>    SEVERE: org.apache.solr.common.SolrException: Error opening new
>> searcher. exceeded limit of maxWarmingSearchers=2, try again later.
>>
>> And, eventually, the voice of doom:
>>
>>    Exception in thread "TP-Processor550" java.lang.OutOfMemoryError:
>> PermGen space
>>
>> Has anybody else experience memory issues related to solr?
>>
>> Thanks,
>>
>> Bill
>>
>>
>>
>> Bill Anderson
>> Software Developer
>> Digital Library Development
>> Georgia Tech Library
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> DSpace-tech mailing list
>> DSpace-tech@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>>
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>
>


-- 
Hilton Gibson
Systems Administrator
JSG Library Room 1025D
Stellenbosch University
Private Bag X5036
Stellenbosch
7599
South Africa

Cell: +27 846 464 758
Email: hgibson__AT__sun.ac.za
------------------------------------------------------------------------------

_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to