I have a scheduled agent set to run every 5 minutes. The problem is that it is running every 6 minutes instead.
Is there a setting on the server or the .ini file that I would need to change to resolve this?
Any insight into this is appreciated.
I have a scheduled agent set to run every 5 minutes. The problem is that it is running every 6 minutes instead.
Is there a setting on the server or the .ini file that I would need to change to resolve this?
Any insight into this is appreciated.
Subject: Agent Schedule
Notes Scheduled agents do not trigger based on time. At the scheduled time (seen by tell amgr sched on console). The agent is moved into the execution queue, The next available executive will execute the agent. This could be several minutes on a busy server with few executives. Once the agent completes, the server time at COMPLETION is used along with your interval to establish the next run time. If your agent takes a minute to complete there is your answer. If the additional minute is a problem then perhaps shceduled agents aren’t suitable for your problem. Sched agents will run, you just can’t guarantee when they run exactly. Keep in mind this is a collaboration and groupware server. It is not ideal for all solutions.
Subject: RE: Agent Schedule
Lee, Thanks for your quick response.
My application is designed to send a request to an application outside domino( to mainframe) and expect data back for the request. But the process is an asynchronous one. I would pick the data for the first request during the next scheduled run. The turn around time must be no more than 10 minutes.
I have no choice but to use schedules agents as we do not want triggered agents. We get around 170,000 request a year.
Short of pulling the plug on the domino is there any other way to ensure that the agent executes every 5 minutes (other than setting it to run every 4 minutes)?
Subject: RE: Agent Schedule
When you say ‘asynchronous’ what do you mean? If nothing in the application changes during the interval what does it do? You can trigger other ways than scheduled, perhaps you need a different approach. Please exlain in detail exactly what is happening.
Subject: RE: Agent Schedule
Reminders – If you decide to schedule the agent every 4 (or 5 or 3) minutes, be sure to consider other agents runnning. Adding multiple threads of AMgr will help ensure that it does not wait on other agents (in other DBs). Only one agent can be actively running in a database at once. If you have multiple agents scheduled in this database, one will always wait for the other to finish (even if multiple threads of AMgr).
Subject: RE: Agent Schedule
Ok, lets say the agent starts running at 1:30 PM. During this run, we send some data in form of flat files to an application running outside domino. The agent terminates after the data has been sent. The original data sent is processed by the remote application and additional information is sent back. At 1:35 the agent starts again. At this time the agent expects to find a flat file that was sent by the remote application in one of the local directories. I cannot expect the data to come back within the same agent run. This is what I meant by asynchronous agent.
Subject: Agent Schedule
Sam,I suggest that you investigate Lotus Enterprise Integrator (LEI) instead of your rather clumsy scheduled agent approach.
Regards
Rolf Pfotenhauer
Subject: Agent Schedule
There is an article on agent scheduling in the Agent FAQ which will help to set your expectation correctly, it is called “Mimizing delays in the agent manager”.