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

IIS7.5: Website freeze on initial request

Hi all,

(Using IIS 7.5 on Windows Server 2008 R2 x64)

When I browse my website first time, page keeps spinning/loading and the it never gets loaded. If I few seconds later try to load it again, everything loads fine. If I come back to my website an hour later, the same problem ... first request fails and following succeeds. So I don't believe it is compiling the page, because then it should only be a problem  on the first request.

Can it have something to do with "recycling"? I have set "Idle time-out" to 0 and Recycling "Regular time interval" to 0.

Before I browse my website, I take a look at "Worker process" and it says that the app pool process is running.

Any idea why my website "falls asleep"?

Thanks!
Mojo
0
M_O_J_O
Asked:
M_O_J_O
  • 3
1 Solution
 
Greg HejlPrincipal ConsultantCommented:
sounds like a resource unavailable issue - website finally stops trying to acquire unavailable resource and then website is cached.  website cache is then cleared and next access tries to load unavailable resource again.

i've used Firebug to discover this sort of issue - it is a plug-in available for firefox.
0
 
M_O_J_OAuthor Commented:
Hi Greg,

Well I can't see what resource it should be. The website hangs even before firebug gets to show anything.

I have 15 websites on that server - thay all do the same (hang on initial request).

Funny thing is that my other new server with Echange 2010 ... owa 2010 also hangs on initial request and I have to stop the browser and enter url again - and then it works.

I've tried with several webbrowsers on several PCs.

I have a new TMG 2010 firewall, but that shouldn't interfeer?

I'm clueless here.

Mojo
0
 
BigRatCommented:
>>I have a new TMG 2010 firewall, but that shouldn't interfeer?

Well in my experience they usually do.

I'd take this out, or at least configure it out and test again. It could be that the thing is incorrectly configured and thinks that the first request is one of a series of DoS attacks.
0
 
M_O_J_OAuthor Commented:
Because I solved it myself.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

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