• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 603
  • Last Modified:

Website hangs causing server to hang

Setup:
I have a server (windows server 2012) with two webistes on two different application pools.  Both websites connect to a SQL Server 2012 database and both are ASP.Net 4.5.  Both use JQuery, VB.Net and ASP.Net.  The only major difference is website two has a membership component (have to sign in) to it where website one does not.  

Problem:
Website 1 runs without any problems.  Website two hangs consistently.  Occasionally it works but most of the time the website just 'spins' when the URL is typed into the browser.  When I look at the ISS event logs it will say something like 'A process serving application pool failed to response to a ping'.  However; trying to access website leads to the whole server going through this process:
1. Server Hard hangs (totally unresponsive--website one starts to hang as well) until the browser is stopped.
2. After browser stops, the server will go into a 'soft hang' (The cursor moves and you can  slowly navigate on server--website one starts to work again).  This will last for about 5 minutes
3. Everything on server is fine.

I suspect it is a setting that deals with ASP.net in IIS, but I'm not sure how to verify this.   I believe this because if I disable my web.config file, the website will work fine.  However, if I have this (and only this) in my web.config:

<?xml version="1.0"?>
<configuration>
  <system.web>
    <compilation debug="true" targetFramework="4.5"/>
    <httpRuntime targetFramework="4.5"/>
</configuration>

Open in new window


the website starts to crash again.

Question:
How do I verify/locate (and stop) the source of the hang?  OR what are some settings I can check?

Thanks!
0
badrhino
Asked:
badrhino
1 Solution
 
Patrick BogersDatacenter platform engineer LindowsCommented:
What if you just comment out line 4, production websites should have debugging disabled.

Doing so causes a number of non-optimal things to happen including:
 
1) The compilation of ASP.NET pages takes longer (since some batch optimizations are disabled)
2) Code can execute slower (since some additional debug paths are enabled)
3) Much more memory is used within the application at runtime
4) Scripts and images downloaded from the WebResources.axd handler are not cached
0
 
badrhinoAuthor Commented:
Sage,  That seemed to worked.  I didn't think about this as the web is still under construction....Thanks!
0

Featured Post

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

Tackle projects and never again get stuck behind a technical roadblock.
Join Now