none
IIS Thread Usage for WCF and Db Connections RRS feed

  • Question

  • I am running a rest interface(using ApiController class) using the ASP.NET 4.6 and IIS 7.5.   The rest interfaces are making a WCF asynch call out to a web service to log all the incoming and outgoing request and response strings for tracking purposes.  The C# code is accessing an Oracle database using the ODP.net 4.112.3.0.

    Under normal load everything works fine on the site in production.  However, when a huge spike in traffic comes (14k requests within 10 minutes) we start to see long response times from the initial request/response logging web service we have and then we see database timeouts.  The database team sees no connection issues on the db server.  My question is are the threads in IIS that are being used to make the outbound wcf asynch web service call the same threads that are used to access the database and thus causing the database timeouts?  If so how can I determine what the max threads are on each machine and how to optimize the usage of the threads?

    Tuesday, November 7, 2017 5:26 PM

All replies

  • Hi kahkao,

    Thank you for posting here.

    For your question is more related to asp.net, you could post a new thread in WCF, ASMX and other Web Services forum for suitable support.

    The CLR Forum discuss and ask questions about .NET Framework Base Classes (BCL) such as Collections, I/O, Regigistry, Globalization, Reflection. Also discuss all the other Microsoft libraries that are built on or extend the .NET Framework, including Managed Extensibility Framework (MEF), Charting Controls, CardSpace, Windows Identity Foundation (WIF), Point of Sale (POS), Transactions. 

    Best Regards,

    Wendy


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.


    Wednesday, November 8, 2017 8:27 AM