Hi, all!
For context, I was asked by our development team that implemented an exception control within our automation scripts in Dataminer
In order to identify if there is any problem with the executions that are sent to the web service of my colleagues,
the foregoing because they have identified a considerable number of lost executions that are registered on the Dataminer side but not on their side
unfortunately in the log it can be seen that many of them return a timeout as shown below:
Question, given this type of timeout, is there any way to know or differentiate if the problem is caused by some kind of queuing on the Dataminer side or by the Web Service of my colleagues?
Or if there is a better approach to the problem described above, we listen to any suggestion
I thank you in advance for any observation or comment that you can share with me, regards.
Hi Christhiam,
From what I understood, I believe that the issue is caused by the destination web server being unable to handle all the requests it is receiving. This results in most requests taking a long time, and others going into timeout.
As suggested by Jorge, you can verify by using Wireshark how much time there is between a request & the response of the destination web server.
You could also ask the team responsible for this webserver to double-check the load and the settings to see whether there are any limits imposed on the number of concurrent connections etc.
You could also increase the timeout on the request-sending logic, but this may cause issues elsewhere because the scripts may take a lot longer to finish.
Thank you very much for your comments, I take note and pass them on to the development team in charge of the web service,
Hi Christhiam, can you describe your script logic? From what I understood, you are making use o c# scripting to make an http to a web server and that request sometimes times out.
Is this correct? If so no DataMiner queuing is involved.
A way to debug is using a tool like Wireshark to verify that communication is fine with your web server or if that is the problem.