Rank: Newbie
Groups: Member
Joined: 12/14/2009
Posts: 7
|
Hello, we're using EO.Web uploaded v 10.0.40.2 and we're getting COMException: The I/O operation has been aborted because of either a thread exit or an application request. (Exception from HRESULT: 0x800703E3).
I guess the exception is thrown (and caught by our logging system) when an IO operation has been aborted ... blah blah blah as it says in error message, but still I have a few concerns:
• COM COM? COM! Is EO Uploader using some horrible COM internally!? Or is some COM exposed by IIS?
• In case this exception happens when user interrupts upload, can it just fail gracefully (no exception, better exception than COM exception with more descriptive message).
Details:
• I don't see any callstack for the COM exception :-(.
• URL: eo_web.ashx?id=4EF2A06E-5171-4166-82A6-242BD1985E8A&uploader_data=ByF1cGxvYWQCVFNjdGwwMF9jdGwwMF9jcGhDb250ZW50X2NwaENNU0NvbnRlbnRfQUpBWFVwbG9hZGVyQXVkaW86Q0hjQW91Z2dWTXRuck5SVHM2ZjVrd2VrMlFnPScmczo0YmYzMzYyYy1iZDRkLTQ4YjgtYTAzYi04ODc3NTg3MzBhZTc=
• UA: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20100101 Firefox/17.0 (I see only this UA in our logs)
• Server: W2008R2 x64
• HTTPS not used
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
Hi,
That's normal. That can occur when the network has a problem, or user closes the browser in the middle of an upload. You can just ignore it.
Thanks!
|
Rank: Newbie
Groups: Member
Joined: 12/14/2009
Posts: 7
|
Can you please be more specific, why it is COMException and not some "normal" exception, like ThreadAbortException?
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,195
|
Hi,
I think you are over concerned about this. We do not use COM in anyway, while IIS uses it extensively. And in case there is an interruption, it's handled by IIS, not by us. So there is no such thing as "failing gracefully" on our part. IIS handles connections, protocols, ASP.NET handles ASP.NET pipe lines, compiling pages, manages page life cycles. We are just a control sitting in the page that renders a portion of the page. These kind of exceptions happens all the time and MS can also change the exception type/message any time. So I think it's completely unnecessary to just look at an exception log and panic about it.
Thanks
|