I am running into a similar issue with Lucene 3.6 which I believe is used in
Solr 3.4.
Following is the exception stack trace:
2012-09-08 18:08:56,341 WARN [STDERR] (Load thread:) Exception in thread
"Load thread" java.lang.OutOfMemoryError: classblock allocation, 2814576
loaded, 2816K footprint
Michael,
Thanks for the response. Below is the stack trace.
Note: Our environment is 64 bit and the Initial Pool size is set to 4GB and
Max pool size is 12GB so it doesn't makes sense why it tries to allocate
24GB (even that is available as the total RAM is 64GB).
This issue doesn't come with SO
Hello, Salman,
It would probably be helpful if you included the text/stack trace of
the error you're encountering, plus any other pertinent system
information you can think of.
One thing to remember is the memory usage you tune with Xmx is only
the maximum size of the heap, and there are other ty
We used JRockit with SOLR1.4 as default JVM had mem issues (not only it was
consuming more mem but didn't restrict to the max mem allocated to tomcat -
jrockit did restrict to max mem). However, JRockit gives an error while using
it with SOLR3.4/3.5. Any ideas, why?
*** This Message Has Been Se
