Using a Program Document to Restart NNTask to Help with Insufficient Memory Crashes on 32bit Platforms

Article:TECH198625  |  Created: 2012-10-19  |  Updated: 2012-10-19  |  Article URL
Article Type
Technical Solution


Crash occurred.  Memory was exhausted and you see the insufficient memory error within the NSD file or the smspanic.txt file.



The crash occurred because memory was exhausted.  This more commonly occurs on 32bit operating systems using database servers like Microsoft Exchange or Lotus Domino where by default programs can only access up to 2GBs or memory.  In the NSD for the fatal stack you may see the following:

This in the fatal stack for nntask and you see the following lines:

and you see this in the stack dump with stack frames section:

you may even see in the following if the process had gotten far enough to start creating the smspanic message to be written to smspanic.txt file:




There are a lot of tweaking options that can be used.  Microsoft came up with the /3GB switch so that Exchange can access up to 3GBs or memory.  There are many options that can be used in the notes.ini file to tweak Lotus Domino also.  The best solution is to upgrade the OS to 64bit on hardware with much more memory. One easy way to resolve this in Domino is to restart SMSDOM on a daily basis because over time private memory builds up in Domino Shared memory as well as SMSDOM private memory.  Most servers will take time, usually about a week, before Domino crashes due to insufficient memory.  One could restart Domino but this is usually not ideal so we will restart SMSDOM.


Go into Lotus Admin client and connect to the server running SMSDOM.  Go to the Configuration tab.  Open Server on left side and choose Programs.  Click the button Add Program.  Make your program document look similar to this one:


Click Save & Close, should look like this now:


Article URL

Terms of use for this information are found in Legal Notices