An HTTP crash on Domino will be either memory or code related (non-memory).
Memory exhaustion defined by “Insufficient memory” messages
Memory Handles defined by “Out of Handles” messages
Custom Web Application or Agent Code
3rd party applications, i.e. DSAPI, other apps running on top of Domino
This article will describe areas in an NSD log for each crash scenario.
1. Memory exhaustion crash
: Console log or the Panic message will report messages related memory such as "Insufficient memory" or "Out of memory".
NSD log from crash will contain memory information for the Domino processes. Below is memory summary for HTTP process from Domino server running on Windows OS.
Note: NSDs from Unix OS, use “Process Heap” size under “Process Heap Memory Stats”
HTTP private memory above is over 1G in size.
Overall HTTP memory is made up of the following areas:
1. Private Static-DPools
3. Thread stack Space
In troubleshooting need to determine where majority of the memory is occurring.
Memory allocations performed by Notes using various DPools (4 MB to 8 MB). These pools are not freed back to the OS after being used.
NSD or Memcheck log look at “Process Heap Memory Stats”
Memory blocks allocated directly from the OS and released back to the OS when freed by the caller
From NSD log search for “Directly Allocated Memory” under memcheck for HTTP process.
Thread stack Space
Generally, each HTTP thread uses about 1 MB of memory per thread
Analyzed NSD showing Thread Stacks memory in “Break Down of Memory (By Component)” table