I’ve been trying to run Domino 6.5.1 on a Windows 2003 server for a few weeks and it seems to be leaking memory like crazy. After running a couple days, all the domino-related processes begin showing that they are each consuming several hundreds of megabytes. And yes, I am keeping the console window minimized down on the taskbar. If I don’t do that, then memory consumption skyrockets even faster. After a couple days runtime, my domino log starts filling up with hundreds of messages like this:
4/13/2004 05:45:53 PM Error connecting to server ANTARES/CWF: The TCP/IP protocol stack reported that it ran out of memory. Consult your network documentation to increase configured memory, or reduce Notes connections by limiting clients (see SERVER_MAXSESSIONS parameter in N
and this
4/13/2004 06:16:56 PM Generic source network failure
and this
04/13/2004 06:25:59 PM The TCP/IP protocol stack reported that it ran out of memory. Consult your network documentation to increase configured memory, or reduce Notes connections by limiting clients (see SERVER_MAXSESSIONS parameter in Notes Admin Guide). - Automatically reducing TCPIP port maximum sessions to 10. Currently, 1 sessions are in the process of being recycled.
The machine is a brand new Dell PE2600 with dual Xeon 3.2GHz HT processors, 4GB ram and tons of disk space. It has a fresh installation of Windows Server 2003. Domino is about the only application running on it right now, except for Trend ScanMail. The machine is an AD controller too, but is presently serving only 4 client workstations since it’s not ready to be thrown into full live production yet, and won’t be unless I can solve this huge memory leaking problem with Domino.
Subject: 6.5.1 on Windows 2003 HUGE memory leaks?
I am having a similar issue. Task mananger is showing each Domino service using 800-900mb or memory.
I was just curious, are you using a virus scanner?? I’m using Mcafee’s Groupshield 5.3. I have six Domino servers and five of them have Groupshield loaded. The sixth server that does not have have Groupshield loaded isn’t having this issue.
Performance doesn’t seem to be affected. The only time I have a problem is when I have to shutdown Domino. It takes way to long.
Subject: RE: 6.5.1 on Windows 2003 HUGE memory leaks?
I also have the same problem. I only upgraded my first server in our domain to r6.5.1 last week and already I have rebooted the server twice to clear this error. I also see other memory errors apart from the TCPIP stack error - “message queue is full” and “insufficient system resources”. I have yet to add the server_maxsessions setting into my notes.ini, but I never had to so this with R5.12 running on the saem box. Why has this started happening? is it a r6.5.1 problem? Should I use just R6.5 for my remaining 10 servers?
Subject: RE: 6.5.1 on Windows 2003 HUGE memory leaks?
hi…
we have updated our Server from Sversion 6.0.3 to 6.5.2 an had now performance/delay problems on Clients while refreshing the Mailbox or an other database. The Server doesn’t show error messages as reported in this thread.
We have installed trendmicro scanmail 5.3 and had this memory issue too.
Our Client are on Version 6.5.1 running on Windows 2000 Professional Edition SP3 or 4
Server OS Version is Windows 2000 Server with SP4
Subject: RE: 6.5.1 on Windows 2003 HUGE memory leaks?
As mentioned in the original post, yes I’m running Trend ScanMail for Domino.
Subject: RE: 6.5.1 on Windows 2003 HUGE memory leaks?
Yes, as mentioned in my proginal post, I’m running Trend ScanMail.
Subject: 6.5.1 on Windows 2003 HUGE memory leaks?
Anyone find a solution to this?
We are seeing the same thing on 6.5.5 and WINDOWS 2003, all the WIN2K servers appear fine.
Dan
Subject: 6.5.1 on Windows 2003 HUGE memory leaks?
We are unaware of any memory leaks with R6.5. Sometime the error you mentioned can be caused by a leak, sometime, by resource contention problems, which cause sessions to be consumed. Either way, the problem warrants a closer look. One way to narrow this down, is to do a netstat -a to collect information about all the TCP connection on this machine. Next to a sh port you_tcpip_portdriver_name. Compare the output of the netstat to the sh port. This will show if the TCP connections are leaking, or not internal memory is leaking. The Netstat may also tell you which service is causing the problems (NRPC port 1352, LDAP port 389, …).
Bottomline, it would be worth while to open up an incident with Lotus Support.