Last post Jul 19, 2018 02:00 PM by DA924
Jul 18, 2018 10:47 AM|asimiq80|LINK
When I send few concurrent hits to A.Call1() then all service methods stuck in IIS most of times and times out, anyone suggest a fix or better design.
I'm using simple HttpBinding, 4.6 .Net Framework with IIS 8.5 and using default throttling settings.
Jul 18, 2018 11:40 AM|mgebhard|LINK
The first step in asking for assistance on a support forum is to explain the overall design and expected results. It is not uncommon for a service to invoke other remote services but it is less common to purposefully chain requests. It is uncommon to lock
IIS which usually means a logic or design bug. It is hard to provide accurate assistance given the vague problem description and design.
First and foremost, WCF is not the best choice for HttpBinding. IMHO, Web API is far better choice because as Web API is REST service framework. WCF will work but WCF is overkill and complex.
In order to better assist you, can you explain what "after some operation" and "get stuck" means and and why service A invokes service B then service B invokes Service C. Are these all remote services calls where A, B, and C are all on different web servers
or are the services all on the same machine. What are these service calls doing and can you explain the design?
Preferably post code that reproduces the issue and/or share your project on GIT so we can see what you're doing.
Jul 19, 2018 02:00 PM|DA924|LINK
You might want to post to the WCF forum as well.