Calling Abort on faulted WCF channel causes server side error to be logged

When a FaultException is returned开发者_JAVA技巧 from my WCF service, I need to Abort the channel instead of Closing it. Both my client and service work fine with this approach but after implementing IErrorHandler on the service and logging any exception, I can see that calling Abort on the client causes the service to log:

System.ServiceModel.CommunicationException: The socket connection was aborted...

I do not want to pollute my service logs with this information and only want to log service related errors. I know I can obviously stop logging any CommunicationExceptions but my service is also a WCF client for other services and CommunicationExceptions raised by these services should be logged.

How can I stop it doing this?

As nobody else has answered the question (Tomas's answer was not relevant), I asked a few experts in the field. Unfortunately, there is no nice way of stopping this and the best that they could come up with was to add logic in IErrorHandler to not log CommunicationExcepions with a message starting with 'The socket connection was aborted'. Not very elegant, but it does work.

The problem is that you get an exception that covers your underlying exception if you get an exception when calling dispose wich is possible. I wrote a wrapper to deal with scenarios like this, you can read about it on my blog: http://blog.tomasjansson.com/2010/12/disposible-wcf-client-wrapper/

The idea is that you have a wrapper around your channel that deals with the scenario if the dispose method throws an exception.

A small example of how you should use my wrapper:

public class ClientWrapperUsage : IYourInternalInterface
{
    public IList<SomeEntity> GetEntitiesForUser(int userId)
    {
        using(var clientWrapper = new ServiceClientWrapper<ServiceType>())
        {
            var response = clientWrapper.Channel.GetEntitiesForUser();
            var entities = response.YourListOfEntities.TranslateToInternal();
            return entities;
        }
    }
}

Here I have assumed that it existing an extension method for a list that contains the entity that is returned by the service, then you use that method to translate it to internal entities. This is 100 % testable, at least I think :). Just moch the interface IYourInternalInterface everywhere you wan't to fake the service.