D
Danny
Hi.
I have an app that is using HttpWebRequest to get data from Web sites.
Occasionally, the CLR throws an IO exception in System.dll that reads
"cannot read from the transport connection." This exception is thrown on
another thread (I am guessing a system thread pool thread). As such, I
cannot catch the exception in the thread from which I invoked the request!
This is very frustrating because ideally, I would like to ignore the
exception and keep fetching more documents from other URLs.
Any suggestions on how to handle this dilemma? I dont control the code from
which the exception gets thrown so I dont have any recourse from my main
thread.
Thanks!
-Danny-
I have an app that is using HttpWebRequest to get data from Web sites.
Occasionally, the CLR throws an IO exception in System.dll that reads
"cannot read from the transport connection." This exception is thrown on
another thread (I am guessing a system thread pool thread). As such, I
cannot catch the exception in the thread from which I invoked the request!
This is very frustrating because ideally, I would like to ignore the
exception and keep fetching more documents from other URLs.
Any suggestions on how to handle this dilemma? I dont control the code from
which the exception gets thrown so I dont have any recourse from my main
thread.
Thanks!
-Danny-