IBM FileNet P8, Version 5.2.1            

The server experiences an out-of-memory condition

An IBM® Content Search Services server is logging an out-of-memory error.

Symptoms

The IBM Content Search Services server generates the following SEVERE message in the server log file:
JVM OutOfMemoryError was thrown by the server. The server will shut down.
Also, the server either shuts down or becomes non-functional:
Platform Symptom
AIX® Non-functional until restarted
Linux Shutdown
Solaris Non-functional until restarted
Windows Shutdown

Causes

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.

Diagnosing the problem

Check for a heap dump to confirm a heap memory problem.

In case the problem persists, save the following files so that they can be evaluated later:
  • Heap dump
  • Stack dump
  • Log files

Resolving the problem

To avoid the recurrence of an out-of-memory error for an IBM Content Search Services server:
  1. If the server is shutdown or non-functional, restart the server.
  2. Change the size for one or more of the following items:
    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:
    • maxTextSize
    • maxBinaryTextSize
    • maxXmlTextSize
    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:
    • inputQueueMemorySize
    • outputQueueMemorySize
  3. Restart the server.


Last updated: October 2015
p8pcs007.htm

© Copyright IBM Corporation 2015.