Agentmanager and tell amgr run

Hello,

we wrote an java agent for schedule purposes.

But sometimes it happens that the Domino Server crashes if the agentmanager kills our agent because the agent has to much work for the configured time. The crash doesn’t happen in all cases and not only if the agentmanager kills the agents (sometimes it happens after 5 minutes), but under solaris more often then under windows.

Now I recognized that the “tell amgr run” command behaves differrently. With this command we have (until noe) no crashes and the agentmanager doesn’t kill the agent because the timeframe is not relevant if the agent has been started in that way.

Now my questions are:

  1. What exactly is different between “normal” schedule and “tell amgr run”? Why does the server crash in one way and in the other not? What is techinically different (load of jvm, start of agent,…)?

  2. Are there any restrictions with us of “tell amgr run” or can we use this command and write a schedule task for it in a productive environment?

Thanks in advance for any help.

Regards,

Christiane

Subject: Agentmanager and tell amgr run

i suppose it’s possible that tell amgr run ignores all time limitations, i don’t know, but it would make sense for it to do that.

then again if your agent is running out of time and being aborted (resulting in a crash) why not just increase the time limits in the server doc so it has enough time to complete?

Subject: RE: Agentmanager and tell amgr run

Unfortunately increasing the time limit in the server doc is not an option, as the agent works on journalized emails and this can take very long.If the time limit would be increased all other agent would be allowed to run longer as well.

Subject: RE: Agentmanager and tell amgr run

then i would suggest limiting it via other means then

ie code it such that it only processes the first 10,000 messages, or run it manullay to figure out how many it can easily process within the time limits and then use that value.