Explanation:
SPR# NGRT67EGPM - A limit was implemented in the server based on the amount
of
memory in use by concurrent NoteOpen transactions (from clients to the server -
local NoteOpens don't count).
This issue was reported to Quality Engineering as SPR# NGRT67EGPM, and was
fixed in Domino 6.5.4 Fix Pack 2.
The fix introduces two new server notes.ini parameters to control the
behavior.
Use either of the parameters below to specify the maximum amount of memory to
be used by concurrent NoteOpen requests processed by the Domino server:
SERVER_MAX_NOTEOPEN_MEMORY_KB= - The maximum number of bytes of
memory
allowed to be used by concurrently opened notes in the Domino server
process.
The value is specified in KB units. For example, setting a value of 10000
will
result in a limit of 10,240,000 bytes.
SERVER_MAX_NOTEOPEN_MEMORY_MB= - The maximum number of bytes of
memory
allowed to be used by concurrently opened notes in the Domino server process.
The value is specified in MB units. For example, setting a value of 10 will
result in a limit of 10,485,760 bytes.
If both notes.ini parameters are used, the SERVER_MAX_NOTEOPEN_MEMORY_MB
parameter takes precedence.
Caution: If the problem is a transient (short lived) lack of virtual address
space due to the opening of many notes, then this feature is useful to prevent
serious problems. However, if the load on the server is constant in nature so
as to exhaust the user address space of the server process, this feature will
NOT solve the problem. In cases where there is heavy traffic opening up many
documents (particularly large documents), these parameters may affect
performance, since once this threshold is exceeded, the opening of additional
documents are queued up until BLK_OPENED_NOTE memory drops below the specified
threshold. In addition, this feature only addresses the case where the Server
process opens a note on behalf of a remote Native Notes Client (NRPC). These
parameters will not be effective for notes that are opened by the server for
its own purposes (such as agents, etc), and will not affect notes opened by
other protocols or tasks, such as Amgr, HTTP, IMAP, SMTP, etc. This has been
reported as a separate issue to Quality Engineering as SPR# PPET6PFLCJ.
Statistics
The following statistics will only be present if one of the notes.ini
settings
are in use. Note that the statistics are updated once a minute:
Server.NoteOpenMemory.Max - The maximum number of bytes of memory allowed to
be
used by concurrently opened notes in the server process.
Server.NoteOpenMemory.Peak - The peak number of bytes in use by concurrently
opened notes in the server process.
Server.NoteOpenMemory.Size - The number of bytes currently in use by
concurrently opened notes in the server process.
Server.NoteOpenMemory.Waited - The number of NoteOpen requests that needed
to
wait for some period of time based on current memory usage.
Server.NoteOpenMemory.Waiting - The number of NoteOpen requests currently
waiting.
Server.NoteOpenMemory.WaitTime - Represents the total time waited for all
NoteOpen requests (currently in 500ms units - e.g. a value of 4 represents 2
seconds of wait time).
Applies to:
Servers
Default Value:
None
UI equivalent:
None, although you can specify this setting in the NOTES.INI Settings tab of
the Configuration Settings document in the Domino Directory.
Syntax:
Server_Max_Noteopen_Memory_KB=Value
Available since:
Lotus Notes/Domino x.x.x
Obsolete since:
Lotus Notes/Domino x.x.x