Troubleshoot IOException on IAsyncResult and HTTPS

#11

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

"John Saunders [MVP]" <john.saunders at trizetto.com> wrote

Quote:

"Martijn van Schie" <mvanschie (AT) newsgroup (DOT) nospam> wrote in message
news:73292969-F6EC-4A86-B4C8-39A7A26309CF (AT) microsoft (DOT) com...
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.EndPostXmlMessageReque st(IAsyncResult
asyncResult)
at TestApplication.ClientProxy.EndVerifyRequest(IAsyn cResult
asyncResultRequest)
at
TestApplication.Async.AsyncVerification.EndAsyncVe rifyRequest(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.

--
--------------------------------------------------------------------------------
John Saunders | MVP - Windows Server System - Connected System Developer

#12

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

"John Saunders [MVP]" <john.saunders at trizetto.com> wrote

Quote:

"Martijn van Schie" <mvanschie (AT) newsgroup (DOT) nospam> wrote in message
news:73292969-F6EC-4A86-B4C8-39A7A26309CF (AT) microsoft (DOT) com...
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.EndPostXmlMessageReque st(IAsyncResult
asyncResult)
at TestApplication.ClientProxy.EndVerifyRequest(IAsyn cResult
asyncResultRequest)
at
TestApplication.Async.AsyncVerification.EndAsyncVe rifyRequest(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.

--
--------------------------------------------------------------------------------
John Saunders | MVP - Windows Server System - Connected System Developer

#13

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

"John Saunders [MVP]" <john.saunders at trizetto.com> wrote

Quote:

"Martijn van Schie" <mvanschie (AT) newsgroup (DOT) nospam> wrote in message
news:73292969-F6EC-4A86-B4C8-39A7A26309CF (AT) microsoft (DOT) com...
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.EndPostXmlMessageReque st(IAsyncResult
asyncResult)
at TestApplication.ClientProxy.EndVerifyRequest(IAsyn cResult
asyncResultRequest)
at
TestApplication.Async.AsyncVerification.EndAsyncVe rifyRequest(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.

--
--------------------------------------------------------------------------------
John Saunders | MVP - Windows Server System - Connected System Developer

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Troubleshoot IOException on IAsyncResult and HTTPS

ASP.net Web Services microsoft.public.dotnet.framework.aspnet.webservices

Re: Troubleshoot IOException on IAsyncResult and HTTPS - 03-10-2008 , 01:59 PM

Re: Troubleshoot IOException on IAsyncResult and HTTPS - 03-10-2008 , 01:59 PM

Re: Troubleshoot IOException on IAsyncResult and HTTPS - 03-10-2008 , 01:59 PM