I’ve got an agent that was running fine until recently, but has started showing an error on execution - Insufficient memory - local heap is full.
It’s a scheduled agent which runs on new and modified documents, with a simple document selection.
The db is 680Mb with 160,000 documents and the server is a Xeon 3GHz with 2GB RAM.
Is this really telling me that the server hasn’t got enough memory left? This is our main mail server used by about 100 users, the agent runs at 10pm every night so the server isn’t busy, although it is in the middle of a compact -b on all databases (just noticed that, maybe that’s an issue).
can anyone shed any light on this?
Thanks
dan
Subject: Agent showing local heap is full
What is your code for the agent?
Subject: RE: Agent showing local heap is full
The agent doesn’t even start running, the error comes when the agent starts to execute.
The code itself runs fine and just loops through the documents adding values to the docs based on a separate document, nothing complex at all.
I’ve had a look at DDM and it says the possible causes are 'because the database could not be opened due to it being compacted or full text indexed which requires exclusive control. ’ It’s not being compacted at the time but I guess the full text indexing could be happening. I might change the time slightly and see what happens.
Dan