m: David Baker
> To: solr-user@lucene.apache.org
> Sent: Thursday, April 16, 2009 6:40:31 PM
> Subject: Re: Garbage Collectors
>
> Otis Gospodnetic wrote:
> > Personally, I'd start from scratch:
> > -Xmx -Xms...
> >
> > -server is not even needed any mor
I would also include the -XX:+HeapDumpOnOutOfMemoryError option to get
a heap dump when the JVM runs out of heap space.
On Thu, Apr 16, 2009 at 9:43 PM, Bryan Talbot wrote:
> If you're using java 5 or 6 jmap is a useful tool in tracking down memory
> leaks.
>
> http://java.sun.com/javase/6/docs
If you're using java 5 or 6 jmap is a useful tool in tracking down
memory leaks.
http://java.sun.com/javase/6/docs/technotes/tools/share/jmap.html
jmap -histo:live
will print a histogram of all live objects in the heap. Start at the
top and work your way down until you find something susp
Otis Gospodnetic wrote:
Personally, I'd start from scratch:
-Xmx -Xms...
-server is not even needed any more.
If you are not using Java 1.6, I suggest you do.
Next, I'd try to investigate why objects are not being cleaned up - this should
not be happening in the first place. Is Solr the
Personally, I'd start from scratch:
-Xmx -Xms...
-server is not even needed any more.
If you are not using Java 1.6, I suggest you do.
Next, I'd try to investigate why objects are not being cleaned up - this should
not be happening in the first place. Is Solr the only webapp running?
Ot
