System.Net.InternalException: System error.
at System.Net.HttpWebRequest.CheckWriteSideResponseProcessing()
at System.Net.ConnectStream.ProcessWriteCallDone(ConnectionReturnResult retur
nResult)
at System.Net.HttpWebRequest.WriteCallDone(ConnectStream stream, ConnectionRe
turnResult returnResult)
at System.Net.ConnectStream.CallDone(ConnectionReturnResult returnResult)
at System.Net.ConnectStream.CloseInternal(Boolean internalCall, Boolean abort
ing)
at System.Net.ConnectStream.System.Net.ICloseEx.CloseEx(CloseExState closeSta
te)
at System.Net.ConnectStream.CloseInternal(Boolean internalCall)
at System.Net.HttpWebRequest.EndWriteHeaders_Part2()
at System.Net.HttpWebRequest.EndWriteHeaders(Boolean async)
at System.Net.HttpWebRequest.WriteHeadersCallback(WebExceptionStatus errorSta
tus, ConnectStream stream, Boolean async)
at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)
at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
at System.Net.ContextAwareResult.Complete(IntPtr userToken)
at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr u
serToken)
at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32
errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32
errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)
这被未处理的异常处理程序捕获。它只是偶尔发生,但带来了灾难性的结果。任何想法如何实际抓住这一个chaps?致命的异常,如何捕捉? System.Net.InternalException:系统错误
UPDATE
现在已经很明显,这只是出现在CPU处于非常高负载下发生的。
@安德鲁真的吗?为什么?你有答案吗? – Tom 2011-05-30 03:33:55
我应该接受哪些问题的答案,我应该选择哪个答案,为什么? – Tom 2011-05-30 03:41:11
谢谢你。我一直在想,所有这些数字和刻度都在哪里。我对你的评论加了一个,所以希望这会给你更多的认可。 – Tom 2011-05-30 04:06:32