reliablesession

问题 WCF Reliable Sessions Fault when Server under heavy CPU load or Thread Pool Busy There appears to be a design flaw in WCF Reliable Sessions that prevents the issue or acceptance of infrastructure keep-alive messages when the server is under high CPU load (80-100% range) or when there isn't an immediate IO threadpool thread available to handle the message. The symptoms manifest as apparently random channel aborts due to reliable session inactivity timeouts. However it appears the abort logic

问题 I am trying to make a WCF service which uses callbacks to the client. I would like the channel to be kept open as long as there is a connection (internet, network) and either the client or channel have not explicitly closed the channel. In order to keep the channel open (even without activity) I found the reliable sessions that WCF supports. I see that by using reliable sessions, there are two timers which one needs to take into consideration: the Binding.ReceiveTimeout and the

问题 I have a client server application. My scenario: .Net Framework 4.6.1 Quad Core i7 machine with hyperthreading enabled Server CPU load from 20 - 70 % Network load < 5% (GBit NIC) 100 users 30 services (some administrative ones, some generic ones per datatype) running and each user is connected to all services NetTcpBinding (compression enabled) ReliableSession enabled each second I do trigger (server side) an update notification and all clients load from the server approx. 100 kB additionally