We are excited to announce that the IIS.NET Forums are moving to the new Microsoft Q&A experience. Learn more >

Classic ASP and .Net Com DLL website hangs on concurrent requestsRSS

1 reply

Last post Feb 01, 2021 05:51 AM by Brucz

  • Classic ASP and .Net Com DLL website hangs on concurrent requests

    Jan 29, 2021 01:43 PM|Yuvaraj C|LINK

    The website hosted in IIS 10, website developed using Classic ASP and .Net Com DLL.

    .Net dll registered by following comment

    RegAsm.exe XXXX.dll /codebase

    Website work fine when single user access the website but when multiple user give the concurrent requests then site starts loading.... and no response received, it's loading until we close the browser window.

    When the website has long loading.... in one browser(chrome), if I tried same website in another browser(firefox) it's working normally but in chrome it's still loading...

    I have verified log details there is No updates in iis log files, but we have logs for other requests until loading issues came

    There is no updates in httperr file.

    If we restart the IIS it took some time to restart and got the following WAS warning in system event log,

    A worker process '####' serving application pool 'XXXXXXXX' failed to stop a listener channel for protocol 'http' in the allotted time. The data field contains the error number.

    Please let me know how to resolve this issue,

    Thanks in advance

  • Re: Classic ASP and .Net Com DLL website hangs on concurrent requests

    Feb 01, 2021 05:51 AM|Brucz|LINK

    Hi Yuvaraj C

    IIS pings a worker process periodically (by default, every 30 seconds) to make sure it is still responsive. It is possible that your worker process is too busy to respond to the ping, so IIS tries to terminate it. When IIS tries to terminate the process, it fails, because the process is still hanging on to areas of memory.

    You can set Ping Enabled to false in advance setting of application pool or increase the Ping Maximum Response Time.

    But I think a better way is to use asynchronous code in the application or increase the concurrent processing capacity of the application.

    Best regards,

    Brucz

    .NET forums are moving to a new home on Microsoft Q&A, we encourage you to go to Microsoft Q&A for .NET for posting new questions and get involved today.