12-01-2014, 05:35 PM
Hi -
I'm trying to diagnose an issue with QM when IntGetFile times out (the timeouts are caused by a server side issue - the server is not responding to requests due do a completely separate issue). The error is handled OK within the thread. But - does anything else in QM (other web service calls, other threads) get blocked if IntGetFile is waiting for a response?
In our application we have a number of different threads (probably between 4 and 8 depending on what's going on). I know that in browsers that they have a small number of connections (IE 9 is on most of the machines - this permits 6 connections while IE 7 only permits 2 - but I don't know what the limit would be in QM).
The issue might be entirely different from this (maybe just bad error handling on my part) but if there are limits in the number of connections that can go through HttpOpenRequest it might help narrow my search. Thanks.
Sean
I'm trying to diagnose an issue with QM when IntGetFile times out (the timeouts are caused by a server side issue - the server is not responding to requests due do a completely separate issue). The error is handled OK within the thread. But - does anything else in QM (other web service calls, other threads) get blocked if IntGetFile is waiting for a response?
In our application we have a number of different threads (probably between 4 and 8 depending on what's going on). I know that in browsers that they have a small number of connections (IE 9 is on most of the machines - this permits 6 connections while IE 7 only permits 2 - but I don't know what the limit would be in QM).
The issue might be entirely different from this (maybe just bad error handling on my part) but if there are limits in the number of connections that can go through HttpOpenRequest it might help narrow my search. Thanks.
Sean