Just Enough Governance for Notes Blog

Bookmark :              

And I have the code to do it too!

One agent that will eat all available memory and crash the server.

Back in my early days of Lotuscript coding I wrote an agent to read and update documents in a lot of db’s on the server. Being the good, know-it-all developer whose code always works, I tested it real thoroughly (Two small db’s on my test server).

Off I went, full of confidence in my work, and scheduled the agent to run during work hours. Well, needless to say, I got lots of calls stating the server was down. Since it was a memory error, I didn’t even suspect it was my code. “Must be a windows issue,” I thought. After scheduling the agent again, and getting a second round of calls, I thought to myself, maybe it is my agent. So I disabled it and did some troubleshooting. I was looping and opening many instances of each document without closing the previous, as well as setting a bunch of other stuff.

So do you have rogue agents in you Domino environment?

If so how do you manage them?

Oh, and no I will not post my code it is too embarrassing