We have recently upgraded to Domino 6.5.1 in the hopes it would sort out our problem - however it hasn't. (According to the documentation, upgrading to 6.5.1 is supposed to fix memory leaks)
Our server has a gradule memory leak. The processor steadily climbs to 100% and the memory slowly climbs, causing freezing and forcing a re-boot every few days.
It isn't the operating system (Windows 2000), as the minute Domino is closed the processor and memory drop dramatically.
The config of the server is more than adequate according to recommendations.
We have about 400 users, 50 databases and run LEI.
Any suggestions would be appreciated.
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.
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.
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!
Discuss This Question: 3  Replies