Agent runonserver delay

We have an agent (agent B) that is called by another agent (agent A) to run on the server. Within agent B, it calls agents C and D.

There seems to be about a 10 second delay from when agents C and D complete to when agent B continues executing at the next line of code after the agent.run command. We determined this by placing a print statement at the last possible lines in agents C and D, and at the next line in agent B, and the log shows a 10 second delay between these print statements.

We have tried executing agents C and D with both agent.run and agent.runonserver, and have gotten the same result both times.

Any ideas? The strange thing here is this only happens in our production environment (on all servers we have tested) but not in our development environment. We have checked all server configuration settings we can think of, with no luck.

Our next step will be to extract the code from an agent and call it directly, but this will require us to have multiple versions of similar code (usually, agent B runs directly on the client, calling agents C and D to run on the server, but we implemented some new functionality that now has agent B running on the server.)

Thanks,

Brian

Subject: agent runonserver delay

how many concurrent agents can be run on the server?

have you ever look at what agents are running at the time you do the run on server event?

Subject: RE: agent runonserver delay

Check if you have remote debugger enabled. A lot of customers who have reported “delays” found that to be the problem. For more details refer to “Troubleshooting agents in R6” in teh Agent FAQ.

Note: The server setting for con-current agents does not control RunOnServer agents.

Subject: RE: agent runonserver delay

Thanks for the feedback… we did check this, and the maximum is 10 agents, and there are no other agents running, so we are not hitting the maximum.