Domino 8.5.1 FP2 Win64 LotusScript Memory errors

I just upgraded a Client’s Web Application server to 8.5.1 FP2. We are getting LotusScript Memory errors in the log and user experience Web Page errors when this occurs. This did not occur on Domino 8.02.

The Web application is heavily used and has extensive use of LotuScript agents (Script Libs, etc)

One of the Exact errors is:

04/06/2010 08:13:26 AM HTTP Web Server: Lotus Notes Exception - LotusScript Error - Memory. [/cal/calendar.nsf/fsurvey?OpenForm&Seq=1]

Sometimes the resource will be an LS agent itself.

Bouncing the server seems to keep the errors at bay for a while, but this has been a daily occurrence (which is not working for us in a prod environment)

I know there has been some discussion on this and I thought this was fixed on 8.5.1 then in FP1 and again in FP2, but it has not. I have been initially holding off moving them to 8.51 because of this, but thought it was finally resolved.

I also found this SPR http://www-01.ibm.com/support/docview.wss?uid=swg1LO45188

Win 2003 64 bit, 8gig memory Domino 8.5.1 FP2

Help!

Subject: Wow, never seen that message before. “Memory.” Huh.

Do let us know what you find.

Subject: No Response??

I guess I am going to need to open a Crit Sit ticket with IBM since no one has any input.

Subject: Please keep us informed, Shawn.

I assumed you’re running 64-bit Domino also?

Subject: Same problem / no fix…

We are experiencing the same problem in a similar situation:

  • Domino 8.5.1 on Win2003/64 server

  • Heavily used web application

We have made a call for this and also referred to: http://www-01.ibm.com/support/docview.wss?uid=swg1LO45188

Reaction from lotus support…

Issue does not happen on the 32 bit version of Windows or on SLES 64 bit

They have added our business case to the existing APAR #LO45188, but there are no plans that it will be fixed in the current codestream.

So they suggested a workaround to restart HTTP task automatically once a week. But this will not help… HTTP task should be quit and loaded at least.

Subject: Apparent Fix

Well, after opening a ticket and gathering NSD info etc, Lotus Support was able to determine that the Memory issues were because the http worker threads were set too high in the server doc. I bumped them down to the recommended max of 80 and the server has been stable for about 10 days. Whereas, it would have encountered the memory error in 1 day.

I also sent a recent NSD so they could look at the memory usage, and they verified it now looked normal.

Shawn

Subject: Restarting just http does not stop memory issues. Must restart Domino

Just an update. Restarting http does not correct these LotusScript out of memory errors. Domino must be restarted.