We have an application that uses runonserver to exceute an agent in the server with some privileges. It’s an agent that takes a lot of time and the user normally has to wait for the agent to end to gain control of teh Notes client.
We have run this agent with no problems in other servers (development and certification) but now that we migrated the application to a production environment the client hangs as if waiting for the agent to terminate for a long time (even when the agent is finished). If I look at the log of the server I can see that the agent runs and ends without problems, but the client stays blocked waiting for the agent to tell him he’s done.
Does anybody know what could be happening??? Maybe there is a config parameter on the server that produces this behaviour??
Subject: Runonserver doesn’t give control back to Notes client
It’s a long shot, but it could be that the user’s session was closed. I’ve noticed that when checking mail or during scheduled replication, the client will open a server session and then close the session. You can see the message on the server console. It could be that while the user is waiting for the agent to finish, the client checks mail and closes the user’s session with the server.
If this is the cause then you should be able to reproduce it by setting a short mail-check internal and executing your RunOnServer process right before the client checks for mail. If the client hangs every time you try it then you know you’ve found the problem.
Subject: RE: Runonserver doesn’t give control back to Notes client
Thanks Willy, I’ll try it out but I doubt this is the reason because in that case I should have the same problem on every server not only in the production server.
Subject: RE: Runonserver doesn’t give control back to Notes client
You were right Will… once I modify the “check email every” to something like 40 minutes the client doesn’t hangs (weird).
The reason this happens only on this server is because the other servers were closed environments without access to email databases, so the email verification didn’t work and the client didn’t hang up while doing the runonserver.
Thanks for your help… let’s see how can I explain this “bug” to the users (they will have to change their email check time eveytime they want to run this agent).
Subject: RE: Runonserver doesn’t give control back to Notes client
When I read your first response the first thing I thought was, “but you only check mail on one server!” LOL!
This seems like another good reason to have a separate mail server.
I don’t know what your process is but maybe it might be better to create a database of requests for this process. Instead of using RunOnServer you create a document in the request database that contains the parameters of your request. A scheduled agent runs and processes the requests and sends an email to the user when it’s done.
Subject: Runonserver doesn’t give control back to Notes client
Under R5, I noticed that an agent that would take a few seconds to complete on the server would not return control to the client for up to a minute. How long are you waiting?
Subject: RE: Runonserver doesn’t give control back to Notes client
The agent takes a lot of time (20 minutes or more). It has always taken that long on the development server and before the client never stayed blocked when the agent ended. Now it does… :-S.
There must be a setting in the server or something different that produces this problem. I can´t think about anything else.