...
> The error occures only once every 10 minutes during a webtest. The trouble
> is that this is very hard to debug because i cannot reproduce the error
[quoted text clipped - 5 lines]
>
> What is the best opproach to tackle this issue.

Signature
--------------------------------------------------------------------------------
John Saunders | MVP - Windows Server System - Connected System Developer
Hi John,
It's hard for me to reproduce it using HTTP, because we are using a test
WebService from a third party authorisation service.
The entire stacktrace comes to this:
Stack Trace :
at System.Net.ConnectStream.InternalWrite(Boolean async, Byte[] buffer,
Int32 offset, Int32 size, AsyncCallback callback, Object state)
at System.Net.ConnectStream.Write(Byte[] buffer, Int32 offset, Int32
size)
at TestApplication.ClientProxy.EndPostXmlMessageRequest(IAsyncResult
asyncResult)
at TestApplication.ClientProxy.EndVerifyRequest(IAsyncResult
asyncResultRequest)
at
TestApplication.Async.AsyncVerification.EndAsyncVerifyRequest(IAsyncResult
asyncResult)
We recently found out that a bug in .NET framework 2.0 sometimes results in
a connection closed causes by a Keep-Alive connection time out. This was
fixed in SP1.
I have asked the customer i they have installer SP1 on there production
machines.
>> Hi,
>>
[quoted text clipped - 14 lines]
> Also, please post the entire exception, including the InnerException and
> stack traces.
John Saunders [MVP] - 10 Mar 2008 18:22 GMT
> Hi John,
>
[quoted text clipped - 15 lines]
> TestApplication.Async.AsyncVerification.EndAsyncVerifyRequest(IAsyncResult
> asyncResult)
That's an interesting pattern of End* method calls. Can you provide an
outline of the pattern of async calling? Is EndPostXmlMessageRequest your
code? Does it explicitly call Write on the stream?
Also, in this case, it's possible that more than just the stack trace may be
interesting. Can you provide the output of ex.ToString()? That is, when you
catch the exception, run ToString on the caught exception, then post the
result. That will include all of the nested InnerException instances.

Signature
--------------------------------------------------------------------------------
John Saunders | MVP - Windows Server System - Connected System Developer
Martijn van Schie - 10 Mar 2008 20:59 GMT
Hi John,
Our customer let me know today that the issue is resolved after installing
SP1.
I agree on the End* stack :). The application is programmed to be very
generic and modulated, and yes, the EndPostXmlMessageRequest is ours. It's
handles the callback from a custom soap request to a webservice proxy using
the HttpWebRequest object.
One problem is that i can't reproduce the issue that easily anymore, as i
installed SP1 on both the test and development machine. I might have a stack
for you from an eventlog backup or issue tracker. I'll try to find one and
post it for you.
Thank you for your time anyways.
Regards,
Martijn
>> Hi John,
>>
[quoted text clipped - 24 lines]
> you catch the exception, run ToString on the caught exception, then post
> the result. That will include all of the nested InnerException instances.