Messages
Reply
Edit
Delete
Have you got solution for the below problem.
I am also facing issue as this.
Thanks in Advance.
Regards,
Deepa
Hi Rick
We often get this error from WCF service:
"System.ServiceModel.FaultException, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 Message : The transaction under which this method call was executing was asynchronously aborted"
We are using the default wsdl proxy which inherits from System.ServiceModel.ClientBase. We are not using any factory to create out the service client. For each request, we create an instance of the proxy, invoke the service and then dispose the proxy. We are also using MSDTC for handling transcations.
try
{
MyServiceClient client = new MyServiceClient (endPoint);
client.DoSomething()
client.Close();
}
catch (FaultException<DefaultFaultContract> ex)
{
}
When we get the asynchronous abort exception, what we see is all clients who are connected to the service also get the same exception and hence we see a series of such exception. I'm not sure if the service enters a faulted state and hence all clients get the same error. I was assuming that since the default InstanceContextMode is PerCall, only the client who got the fault exception should get kicked out and not all other clients. I don't see any events for app pool recycle too.
We enabled tracing and saw this as the actual exception:
<InnerException>
<ExceptionType>System.IO.PipeException, System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
<Message>There was an error reading from the pipe: The pipe has been ended. (109, 0x6d).</Message>
<StackTrace>
at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)
</StackTrace>
<ExceptionString>System.IO.PipeException: There was an error reading from the pipe: The pipe has been ended. (109, 0x6d).
at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)</ExceptionString>
</InnerException>
Any idea what could be going wrong?
Regards
Rajesh