Domino server memory leaks

Lennonitpe
pts.
Tags:
Lotus Domino
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.
Asked: Last updated:
Related Questions

Answer Wiki

Thanks. We'll let you know when a new response is added.

That depends where your server is freezing. Maybe it’s an agent that don’t terminate, a Java Agent that don’t free up memory, a database that is corrupt. There would be one possibility that we check the server and do a monitoring on it to find the problem. If this interests you: contact me at office@nimbus.at

greets

Michael

Discuss This Question: 3  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Jdduff
    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.
    0 pointsBadges:
    report
  • Schalk
    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.
    0 pointsBadges:
    report
  • Maggs
    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.
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: