---

The following memory warnings are indicative of low memory conditions involving the exhaustion of a Domino process’s memory handles. Domino administrators can monitor the Domino console for these specific errors and take the appropriate actions for data collection and server recovery:

The above warnings can occur in conjunction with the following generic memory errors:

The warnings are generated when Domino private handle limits have been reached.

An exception is with the following entry, which can occur in relation to shared or private memory; however, the majority of issues are associated with private handle exhaustion due to the lower limits.


Actions to take

The following debug should be enabled by default and are necessary for initial root cause analysis pertaining to all categories of Domino server outages. These may be set dynamically at the Domino server console using the set config command (for example: set config debug_threadid=1)
The following logs should be collected when the memory errors are being generated. These logs will contain the initial data necessary to determine which task and their respective memory block(s) are utilizing excessive amounts of memory handles:

A) Execute the following command at the Domino console:
B) Capture two NSDs manually, taken 2 minutes apart, executed at the time the memory warnings are being generated should be collected:
C) Console log

D) Additional troubleshooting may require the collection of additional data or memory dumps:

Recovery after data collection

The console log should be monitored and reviewed for the following errors:
The review of the console should focus on determining if the memory errors are generated by one particular process or multiple processes. Memory related issues relating to private memory will be characterized by one particular task repeatedly reporting the warnings. Also determine if a particular activity is triggering the errors such a particular agent executing. Once the data has been collected, an attempt at recycling the task can be made to recover proper functioning of the server. If a particular action is associated with the entries, you can also attempt to disable the action. For example, if a particular mail message or agent is triggering the errors, then you can attempt to recycle the router or shut Domino down to recreate the mail.boxes, or disable the specific agent.

Specifically, the warning LSXBE: ****** Out of Backend Memory****** commonly occurs when a Domino process exhausts backend memory handles. Particularly, this condition can occur when Java code is cycling large amounts of data or View Entry objects and the recycle() code for Java objects is not implemented. The Java code can either be executed within an agent, servlet or standalone application connecting to Notes or Domino through local Java API.

The following Domino processes are normally implicated with the error and can be recycled in an attempt to recover the memory:
The next objective is to review memory related configuration settings within the notes.ini. Then determine if there is a specific memory block associated with the process that is utilizing large amounts of handles. This step will most likely be performed by the IBM Lotus Support Analyst.

Recommendations

Beginning with Domino 8.5.3, the limits for the available private and shared handles has increased for all platforms excluding 32-bit Domino for AIX and Solaris:
Consider upgrading to the latest release of Domino and 64-bit version to benefit from the increased handle limits. However, if the Domino outages are relating to a memory leak, the increased handle limits may delay the outage but additional troubleshooting will be required to further isolate the cause of the leak.

Related Documents