What qualifies as a 'Concurrent' agent

HCL Domino Domino Forum
1

It’s my understanding that the maximum number of concurrent agents that can be set on a server document is 10. I have some questions concerning this:

1.) What is considered a ‘concurrent’ agent. This would seem to include scheduled agents, but does it also include event driven agents, including those in web applications?

2.) Are WebQueryOpen and WebQueryExit agents excluded from this limitation on concurrent agents?

3.) I’ve heard that a Java agent which is run by a LotusScript agent is automatically subject to the restriction on concurrent agents. Is this correct?

4.) Is there some work-around to the limit of 10 concurrent agents being set on the server document?

Thanks very much.

2

Subject: What qualifies as a ‘Concurrent’ agent

  1. The number of concurrent agents means agents which are running scheduled by the Agent Manager and all in different databases. No agents in the same database can ever run simultaneously via the Agent Manager. Agents which are started from the Web have nothing to do with the agent manager, and they are purely core tasks of the HTTP server - you don’t see them anywhere. There is also a setting for running HTTP agents simultaneously for the notes.ini: DominoAsynchronizeAgents=1, and also a time limit for web agents: WebAgentTimeLimit=value (value: 0=forever, else time in seconds). This is a VERY important setting, as an accidentally looping agent can jam you whole server’s CPU load up to 50% and beyond, and your only chance to stop the agent is to DOS: “nsd -kill” (don’t even bother to try “tell http restart”, “tell http quit”, or “q”).

  2. I don’t think so, as I believe that all HTTP agents are run via the same internal agent processor of the HTTP task.

  3. No idea.

  4. Is there a need for? I always say that if an agent runs longer than 30 seconds, it should not run on a production server. Also, every agent should have a built in stop and go logic, which can be configured in a database, for example: allow to run 30 seconds, then stop for 5 minutes, rinse and repeat. If you have several long lasting agents (longer than 30 seconds without stop and go logic) get a heavyload server which runs all the long lasting, poorly coded agents and replicate data to the real servers when they are done with the updates.

3

Subject: RE: What qualifies as a ‘Concurrent’ agent

Thanks Mika. Your response was very informative.