WCF-NetNamedPipe Adapter Is Not Disposing of ChannelFactory
4/20/2012 8:08:33 AM
User(s) can reproduce this bug
I have a WCF service, hosted in IIS 7.5 / WAS, that is exposed through an endpoint using the NetNamedPipe binding. I am sending to this service via a Solicit-Response send port using the WCF-NetNamedPipe adapter. This send port is not using SSO.
The trace log for this service rapidly accumulates "Throwing an exception" trace entries (http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.ThrowingException.aspx) in the root activity that are recording the following two exceptions:
System.ServiceModel.CommunicationException, System.ServiceModel, Version=188.8.131.52, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.IO.PipeException, System.ServiceModel, Version=184.108.40.206, Culture=neutral, PublicKeyToken=b77a5c561934e089
With the message:
There was an error reading from the pipe: The pipe has been ended. (109, 0x6d).
It appears that the WCF adapter is not disposing of the channel factory that it is using and thus abruptly ending the pipe.
BizTalk 2010 Beta
1. Set up a WCF service exposed through a NetNamedPipe binding.
2. Enable tracing on the service
3. Create Solicit-Response send port in BizTalk to interact with the service using the WCF-NetNamedPipe adapter.
4. Send a message through to the service.
5. Check the trace log for the exceptions noted above.
to post a comment.
Please enter a comment.
to post a workaround.
Please enter a workaround.
© 2013 Microsoft