In recent development, it has always been found that a large number of users will inevitably die, or the user will directly drop the line. I don't know why, because the project uses netTcp binding, conjecture may be about concurrent connections. So I checked:
In Windows 7, the default number of concurrent connections is 10.
Code <Binding name = "netTcpBindConfig" closeTimeout = "00:30:00"
OpenTimeout = "00:30:00" receiveTimeout = "00:30:00" sendTimeout = "00:30:00"
TransactionFlow = "false" transferMode = "Buffered" transactionProtocol = "OleTransactions"
HostNameComparisonMode = "StrongWildcard" listenBacklog = "10"
MaxBufferPoolSize = "2147483647" maxBufferSize = "2147483647" maxConnections = "10"
Maxcompute edmessagesize = "2147483647">
After the project is transplanted to windows server, the number of concurrent connections needs to be changed.
Code <Binding name = "netTcpBindConfig" closeTimeout = "00:30:00"
OpenTimeout = "00:30:00" receiveTimeout = "00:30:00" sendTimeout = "00:30:00"
TransactionFlow = "false" transferMode = "Buffered" transactionProtocol = "OleTransactions"
HostNameComparisonMode = "StrongWildcard" listenBacklog = "10"
MaxBufferPoolSize = "2147483647" maxBufferSize = "2147483647" maxConnections = "1000"
Maxcompute edmessagesize = "2147483647">
However, the problem still exists, and you need to configure the behavior, so the number of connections for the behavior also changes.
Code <Behavior name = "JXSoft. JPlan. WCFService. Behavior">
<ServiceThrottling maxconcurrentcils = "1000" maxConcurrentInstances = "1000" maxConcurrentSessions = "1000"/>
<ServiceMetadata/>
<ServiceDebug includeExceptionDetailInFaults = "true"/>
<DataContractSerializer maxItemsInObjectGraph = "6553600"/>
</Behavior>
The problem has been solved, and no longer has been stuck or dropped.