I'm trying to find answers to my questions about ServerXMLHttp... We
have the following (simplified) piece of VB6 code on a component,
that is accessed thousands of times per day:
---
On Error Goto Erro
lResolve = 2 * 1000
lConnect = 2 * 1000
lSend = 10 * 1000
lReceive = 6 * 1000
Set objHTTP = New ServerXMLHTTP 'msxml3.dll
objHTTP.setTimeouts lResolve, lConnect, lSend, lReceive
objHTTP.open "GET", strURL, True
lngDiffTempo = GetTickCount()
objHTTP.send
iTimeout = 0
Do While objHTTP.readyState <> 4
objHTTP.waitForResponse 1
iTimeout = iTimeout + 1
If iTimeout > 12 Then Goto Erro
Loop
If objHTTP.Status = 200 Then
lngDiffTempo = GetTickCount() - lngDiffTempo
End If
Exit Function
Erro:
lngDiffTempo = GetTickCount() - lngDiffTempo
---
But even though the sendTimeout is 10 seconds, the waitForResponse
raises a lot of -2147012894 errors in less than 10 sec! We log that
"lngDiffTempo" var, and registered from 2.000 to 9.500 milliseconds
when this error happens. Shouldn't this error happen only when the
total time is more than 10 sec?
And how can we identify the real causes of getting this -2147012894
error so many times? In 800 queries to the destination site, we
logged 150 errors of this type. Somebody here told that this could be
a serialization of the WinHttp component: some requests don't get to
the destination site because WinHttp is not being able to handle so
many requests.
Thanks in advance,
Ytsejammer
Posted Via Usenet.com Premium Usenet Newsgroup Services
----------------------------------------------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
----------------------------------------------------------
http://www.usenet.com