8gmaker

It makes me confused ,too

@MattB-msft is the MaxConnectionTimeout the same as the execution timeout, I see the default value of MaxConnectionTimeout is 2 minute, but we see some execution timeout of 4 minute

We now create a connection pool of ServiceClient, there is a parent client with its clones, when the pool is ready to delete, we dispose the parent and clones

@MattB-msft https://docs.microsoft.com/en-us/dotnet/framework/wcf/samples/use-close-abort-release-wcf-client-resources WebProxyClient is derived from ClientBase, but I dont see the Close or Abort methods get called in the code. https://github.com/dotnet/wcf/blob/580ce66ac5def05f67186681595a9748f6bdf135/src/System.Private.ServiceModel/src/System/ServiceModel/ClientBase.cs#L407

@MattB-msft Could you help have a look at this issue, we are now using this sdk and will release at the end of this month, Thanks

Thanks for the information, by the way, we use .net core, I don't know whether the implementation of WCF in .net core is different

I think you can use Lazy pattern to avoid time cost of Create a ServiceClient, so you Startup will finish soon without be blocked by the constructor

I also see this behavior sometimes

@Ivan-Colomer The line: ```csharp var json = await sResp.Content.ReadAsStringAsync().ConfigureAwait(false); ``` already reads all the content and buffer it into memory, so there is no need to dispose the HttpResponseMessage. For...

@xperiandri do you solve this now ?