On Saturday 03 September 2011 20:09:54 Michael Bell wrote: > 2011-08-30 13:01:31,489 [TP-Processor8] ERROR > com.gwava.utils.ServerErrorHandlerStrategy - reportError: > nastybadthing :: > com.gwava.indexing.lucene.internal.LuceneSearchController.performSear >chOperation:229 :: EXCEPTION : java.lang.OutOfMemoryError: Requested > array size exceeds VM limit java.lang.OutOfMemoryError: Requested > array size exceeds VM limit at > org.apache.lucene.search.FieldCacheImpl$StringIndexCache.createValue( >FieldCacheImpl.java:624) at > ... > Looking at the sort class, the api docs appear to say it would create > an element of 1.2 billion items (4*300m). Is this correct? Is the > issue going beyond signed int32 limits of an array ( 2 billion items) > or is it really a memory issue? How best to diagnose?
Call your java process this way java -XX:HeapDumpPath=. -XX:+HeapDumpOnOutOfMemoryError and drag'n'drop the resulting java_pid*.hprof into eclipse. You will get an outline by class for the number and size of allocated objects. Note that you need somewhat more main memory for the post mortem diagnosis, so you may want to start your java process with less than 24 GB. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
