Comments on: Domino server memory leaks

By: maggs

maggs — Fri, 06 Aug 2004 12:55:31 +0000

We use an automated batch file to down the server and restart it on a scheduled basis, minimum of weekly. At times we have done this nightly.

By: schalk

schalk — Fri, 06 Aug 2004 12:50:40 +0000

Java servlets run on the Domino JVM are a frequent cause of memory leaks. Make sure that you have increased the number of threads available to a minimum of 128. Be sure that your servlets collecting garbage fast enough.

LEI, if there is use of JDBC, virtual docs, real-time, may be running agents that are not properly tuned.

Make sure that you have increased the number of agents allowed to run concurrently beyond the default minimum to at least 5.

Finally – you need to let the server crash, and collect the NSD files to send to Lotus. You also need to be analyzing the plain old log data to see what’s running when the leak begins.

By: jdduff

jdduff — Fri, 06 Aug 2004 12:24:33 +0000

Memory leaks are common in every Domino Release. We always enlist IBM’s (tech support) help in identifying the source of the leak and whether or not it is a known problem. Afterall, as Lennonitpe said, it could be one of your agents or databases. If you can afford to, turn off AMgr for a couple of days (not likely) or run hourly “server -m” commands to dump memory. Those dumps could reveal when the greatest buildups occur and give you clues as to what causes them.