The request channel timed out while waiting for a reply after 00:00:59.9529971. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding.
2 replies
Last post Dec 06, 2018 02:12 AM by Abraham Qian
Last post Dec 06, 2018 02:12 AM by Abraham Qian
Member
6 Points
87 Posts
The request channel timed out while waiting for a reply after 00:00:59.9529971. Increase the time...
Dec 05, 2018 09:51 AM|Ravindranath M|LINK
Hi,
while consuming svc in client, facing the error as "The request channel timed out while waiting for a reply after 00:00:59.9529971. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a long".
I am using the below config settings.
<bindings>
<basicHttpBinding>
<binding name="BasicHttpsBinding" closeTimeout="00:50:00" openTimeout="00:50:00" receiveTimeout="00:50:00" maxReceivedMessageSize="99999999" maxBufferSize="99999999" maxBufferPoolSize="2147483647">
<readerQuotas maxDepth="32" maxArrayLength="2147483647" maxStringContentLength="2147483647" />
<security mode="Transport" />
</binding>
</basicHttpBinding>
</bindings>
Any other settings need to modify in web.config.
Contributor
4963 Points
4218 Posts
Re: The request channel timed out while waiting for a reply after 00:00:59.9529971. Increase the...
Dec 05, 2018 10:19 AM|DA924|LINK
Your timeout settings seem a little suspect from 1 minute, the default, to 50 minutes? Maybe, you should find out what is taking so long on the service-side to complete giving control back to the client that giving control back to the client can't complete due to a timeout. Services in SOA should be quick hitters in and out in a few seconds when the client uses the service.
Member
740 Points
321 Posts
Re: The request channel timed out while waiting for a reply after 00:00:59.9529971. Increase the...
Dec 06, 2018 02:12 AM|Abraham Qian|LINK
Hi Ravindranath M,
There is nothing wrong with your configuration, and don’t forget to apply the binding configuration to the service endpoint.
I have encountered this problem when testing WCF service. I don’t think simply increasing the timeout limit will solve the problem. This may be caused by other problems, such as the network issue. I suggest you provide more detail about your project which could still reproduce your problem.
Feel free to let me know if there is anything I can help with.
Best Regards
Abraham