When you first run the Domino Log Analyzer against your DomLog.nsf there may be to many hits in DomLog.nsf to be processed within the time allowed for the agent to run (see the settings in your server document). You may want to increase these time to allow the agent to run longer. However, if the log is very large even this may not be enough to let the agent run to completion.If your DomLog.nsf is large we would suggest the following:
- Stop the HTTP task and rename the DomLog.nsf to DomLogOld.nsf (or something similar).
- Create a new DomLog.nsf from the template and copy the two views and agents from the Additional Design database into the new DomLog.nsf
- Re-start the HTTP task and logging will start into the new DomLog.nsf
- Later you can point the Log Analyzer to the Old DomLog.nsf and allow it to selectively process the older hits.
Another option would be to:
- Select all of the documents in the DomLog.nsf
- Run the agent "Set To Processed"
- Periodically select groups of documents and run the agent "Set To UnProcessed". You should experiment a bit with how many documents to select at a time to insure that the agent can run through to completion in the time allowed.
If the Domino Log Analyzer agent is terminated by the Agent Manager because of an "Out of Time" situation you might find that there is a significant memory bleed. This is because the Agent Manager does not do a logical shut down of the agent, and allocated memory may not be freed up. The only solution to this shut down the Domino server and re-start it. If memory allocation is still high you may have to re-cycle the server.This memory allocation situation is beyond our control, so we suggest some preventative measures be taken.