An IBM® Content Search Services server is logging an out-of-memory error.
JVM OutOfMemoryError was thrown by the server. The server will shut down.
Platform | Symptom |
---|---|
AIX® | Non-functional until restarted |
Linux | Shutdown |
Solaris | Non-functional until restarted |
Windows | Shutdown |
During indexing and searching, IBM Content Search Services consumes heap memory for document analysis, preprocessing and indexing queues, and index memory structures. If the heap memory size (along with the queue size and file size limits) is not configured appropriately, the JVM can run out of memory.
For search servers, the minimum amount of memory that is needed can be affected by the number of queries that you run concurrently.
Check for a heap dump to confirm a heap memory problem.
Item | Guideline | Parameter |
---|---|---|
Heap | Increase the size of the heap. For more information,
see the following topics:
|
Configuration tool parameters. Set the value of the maxHeapSize parameter. |
File | The heap memory size affects the file size limits that might be needed. For more information, see 'Heap memory consumption" in Parameters that influence performance. If truncation errors can be avoided, reduce the file size limits. For information about truncation errors, see Text extracted from a document during indexing is truncated. |
Configuration tool parameters.
Set the value of the following parameters:
Important: The latter two parameters can cause documents
not to be indexed if the file size limit is exceeded.
|
Queue | Reduce the size of the input and output queues. For more information, see Troubleshooting queues. |
Configuration tool parameters.
Set the value of the following parameters:
|