I am hitting into a problem with my company application.
I am going to summarize the system key elements:
- My company's system is running since few years on Windows XP and 7 (Home, Pro, Basic) machines.
- It has been written in .NET 4.0 and based upon WCF.
- It uses the default throttling values (MaxConcurrentSessions = 100 * CPU (4) : enough for our workload).
- The main service is hosted by a stand alone deamon process (not IIS).
- The main service is configured as Multithraded/PerSession instances.
- The protocol is Reliable NET.TCP.
- No more than 10 clients access concurrently the service.
The problem is that only on Windows 7, intermittently, I get (I discovered that by the WCF full trace log) a "Server too busy exception" due to an exhausted MaxConcurrentSessions limit (impossible!!!).
Do you have any idea about this strange behaviour?
Thank you and have a Happy New Year!
Antonio