I am currently attempting the same thing. I am calling more than one async
method on the wse generated service client at a time and get these errors
when submitting two requests that complete at different times:
When the last in is the first out, last in completes successfully, then
"WSE007: The SoapEnvelope or its SoapContext has already been processed by a
Pipeline." once the first in completes...
When the first in is the first out, first one finishes with "WSE911: Fail to
receive the response message."
Are concurrent async methods not supported on the wse generated client? Is
this a setting that I need to change? Anyone else solved this?
Thanks.
~Chris S
[quoted text, click to view] "nbevans@gmail.com" wrote:
> Hi,
>
> I'm getting several sporadically occuring errors using WSE 3.0. I'm
> using a Windows Service to host the web service - therefore using
> soap.tcp://.
>
>
> The errors only seem to occur when using asynchronous calls.
>
>
> WSE007 The SoapEnvelope or its SoapContext has already been processed
> by a Pipeline
>
>
> WSE911 Fail to receive the response message
>
>
> WSE102 The asynchronous operation has already completed. Invoke just
> once the End portion of an asynchronous operation, with an instance of
> IAsyncResult
>
>
> All components of the client and web service are running on my local
> Windows XP x64 machine so there's definately not any connection
> problems occuring.
>
>
> Any ideas?
>
I am currently attempting the same thing. I am calling more than one async
method on the wse generated service client at a time and get these errors
when submitting two requests that complete at different times:
When the last in is the first out, last in completes successfully, then
"WSE007: The SoapEnvelope or its SoapContext has already been processed by a
Pipeline." once the first in completes...
When the first in is the first out, first one finishes with "WSE911: Fail to
receive the response message."
Are concurrent async methods not supported on the wse generated client? Is
this a setting that I need to change? Anyone else solved this?
Thanks.
~Chris S
[quoted text, click to view] "nbevans@gmail.com" wrote:
> Hi,
>
> I'm getting several sporadically occuring errors using WSE 3.0. I'm
> using a Windows Service to host the web service - therefore using
> soap.tcp://.
>
>
> The errors only seem to occur when using asynchronous calls.
>
>
> WSE007 The SoapEnvelope or its SoapContext has already been processed
> by a Pipeline
>
>
> WSE911 Fail to receive the response message
>
>
> WSE102 The asynchronous operation has already completed. Invoke just
> once the End portion of an asynchronous operation, with an instance of
> IAsyncResult
>
>
> All components of the client and web service are running on my local
> Windows XP x64 machine so there's definately not any connection
> problems occuring.
>
>
> Any ideas?
>
I am currently attempting the same thing. I am calling more than one async
method on the wse generated service client at a time and get these errors
when submitting two requests that complete at different times:
When the last in is the first out, last in completes successfully, then
"WSE007: The SoapEnvelope or its SoapContext has already been processed by a
Pipeline." once the first in completes...
When the first in is the first out, first one finishes with "WSE911: Fail to
receive the response message."
Are concurrent async methods not supported on the wse generated client? Is
this a setting that I need to change? Anyone else solved this?
Thanks.
~Chris S
[quoted text, click to view] "nbevans@gmail.com" wrote:
> Hi,
>
> I'm getting several sporadically occuring errors using WSE 3.0. I'm
> using a Windows Service to host the web service - therefore using
> soap.tcp://.
>
>
> The errors only seem to occur when using asynchronous calls.
>
>
> WSE007 The SoapEnvelope or its SoapContext has already been processed
> by a Pipeline
>
>
> WSE911 Fail to receive the response message
>
>
> WSE102 The asynchronous operation has already completed. Invoke just
> once the End portion of an asynchronous operation, with an instance of
> IAsyncResult
>
>
> All components of the client and web service are running on my local
> Windows XP x64 machine so there's definately not any connection
> problems occuring.
>
>
> Any ideas?
>
Don't see what you're looking for? Try a search.
