I set up a WCF Service that is based on NetTcpBinding and I am using localhost. Client and Host run on same machine. I get a communication exception in the client consuming a specific method of the interface of the WCF Service in a while loop. The while loop is mandatory, because I am monitoring a value and action depends on change in value. The client is a clr console application and contains a dll with the service reference and the app.config file for the client.
For trying to solve the problem I increased the openTimeout, closeTimeout, receiveTimeout, sendTimeout, maxBufferPoolSize and maxReceivedMessageSize in the binding configurations, but without any success.
I also let the thread of the client sleep so that the method of the interface is less often called, but also without any success.
To give you an idea, below you can find the while loop of the client that calls the method of the interface. I also attached the binding configurations of the client.
While loop:
while (ClientOfIPCService.getUGUDasDouble(ControlUGUD) == ValueOfControlUGUD)
{
Console::WriteLine("Request acProgState...");
CurrentProgStat = ClientOfIPCService.getNCKVariableWithPathasDouble("/Channel/State/acProg[u1,1]");
if (CurrentProgStat == 0 || CurrentProgStat == 3 || CurrentProgStat == 4)
{
exit(0);
}
}
My question now is how to solve this problem? Is there any possibility that I empty the buffer of the requests? How can I avoid this Communication Exception?
Update 01/08/2019:
complete App.config file of Host:
<system.serviceModel>
<behaviors>
<serviceBehaviors>
<behavior name="MexGet">
<serviceMetadata httpGetEnabled="false" httpsGetEnabled="false" />
<serviceDebug includeExceptionDetailInFaults="true" />
</behavior>
</serviceBehaviors>
</behaviors>
<!--Binding Settings-->
<bindings>
<netTcpBinding>
<binding name="BindingConfig1"
closeTimeout="00:30:00"
openTimeout="00:30:00"
receiveTimeout="00:30:00"
sendTimeout="00:30:00"
maxReceivedMessageSize="20000000"
maxBufferSize="20000000"
maxBufferPoolSize="20000000">
<readerQuotas maxDepth="32"
maxStringContentLength="20000000"
maxArrayLength="20000000"
maxBytesPerRead="20000000"/>
</binding>
</netTcpBinding>
</bindings>
<!--Service Binding-->
<!--2. Configure end point with netTcpBinding-->
<services>
<service behaviorConfiguration="MexGet"
name="PROKOS_IPC_SERVER.HMI_IPC">
<endpoint name="NetTcpBindingEndpoint"
address=""
binding="netTcpBinding"
bindingConfiguration="BindingConfig1"
contract="PROKOS_IPC_SERVER.IHMI_IPC">
<identity>
<dns value="localhost" />
</identity>
</endpoint>
<!--3. Configure the meta data exchange end point-->
<endpoint name="MexTcpBidingEndpoint"
address="mex"
binding="mexTcpBinding"
bindingConfiguration=""
contract="IMetadataExchange">
<identity>
<dns value="localhost" />
</identity>
</endpoint>
<host>
<baseAddresses>
<add baseAddress="net.tcp://localhost:8124/HMI-IPC" />
</baseAddresses>
</host>
</service>
</services>
complete App.config file of the Client:
<system.serviceModel>
<!--Binding Settings-->
<bindings>
<netTcpBinding>
<binding name="BindingConfig1" closeTimeout="00:30:00" openTimeout="00:30:00"
receiveTimeout="00:30:00" sendTimeout="00:30:00" maxBufferPoolSize="20000000"
maxReceivedMessageSize="20000000" />
</netTcpBinding>
</bindings>
<client>
<endpoint address="net.tcp://localhost:8124/HMI-IPC" binding="netTcpBinding"
bindingConfiguration="BindingConfig1" contract="IPC.IHMI_IPC"
name="NetTcpBindingEndpoint">
<identity>
<dns value="localhost" />
</identity>
</endpoint>
</client>
</system.serviceModel>
And here I attached a screenshot of the Server stack trace:
The complete error message of the client is: "The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:29:59.9549975'."
I didn't handle the exception on the client side which gives me the following error message in my clr console application.
Update 02/08/2019:
The following code shows the idea of letting the thread sleep to avoid many requests:
while (ClientOfIPCService.getUGUDasDouble(ControlUGUD) == ValueOfControlUGUD)
{
delay(500);
Console::WriteLine("Request acProgState...");
CurrentProgStat = ClientOfIPCService.getNCKVariableWithPathasDouble("/Channel/State/acProg[u1,1]");
if (CurrentProgStat == 0 || CurrentProgStat == 3 || CurrentProgStat == 4)
{
exit(0);
}
// lets the current thread sleep for X miliseconds
delay(500);
}
The other idea is to integrate a method where I can cut the wire after the while loop and to open it again for further use.
Update 02/08/2019:
I enabled the WCF tracing as required and I could get the following exception details from the tracing (see screenshot and the translation below of the message):
"The socket was aborted because an asynchronous receive from the socket was not completed within the assigned time limit of 00:02:00. The time period allocated for this task may have been part of a longer timeout."
