Hello.
The server has much more memory. I have given minimum 8 GB to
Application Server..
The Java opts which are of interest is : -server -Xms8192m -Xmx16384m
-XX:MaxPermSize=8192m
Even after giving this much memory to the server, how come i am hitting
OOM exceptions. No other act
Hello,
The following exception is being printed on the server console when
trying to index. As usual, indexes are not getting created.
java.lang.OutOfMemoryError: Java heap space
at
org.apache.lucene.util.AttributeSource.(AttributeSource.java:148)
at
org.apache.lucene.util.Attribut
Can someone please suggest what might be the possible resolution for the
issue mentioned in trailing mail::
Also now on changing some settings for IndexWriterConfig and
LiveIndexWriterConfig I get the following exception:
20:31:23,540 INFO java.lang.OutOfMemoryError: Java heap space
20:31:2
The exact point at which a java program hits OOM is pretty random and
it isn't always fair to blame the chunk triggering the exception.
callMethodThatAllocatesNearlyAllMemory();
callMethodThatAllocatesABitOfMemory();
and the second one hits OOM, but is not to blame.
Anyway, your base problem see
Ankit,
The stack traces you are showing only say there was an out of memory
error. In those case, the stack trace is unfortunately not always
helpful since the allocation may fail on a small object because
another object is taking all the memory of the JVM. Can you come up
with a small piece of co
I've noticed that processes that were previously IO bound (in 3.5) are now CPU
bound (in 4.4) and I expect it is due to the compression/decompression of term
vector fields in 4.4.
It would be nice if users of 4.4 could turn the compression OFF entirely.
-Original Message-
From: Iva
