Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1129
  • Last Modified:

Web Server takes long time to respond on first request

I've got a W2K3 R2 Server running IIS

Here is what is strange. Any initial web request coming takes like 7-15 seconds to be responded to, but after that, it's fine and there is no delay.

This is also the case when trying to GO TO any web site out on the Internet from the server.

I also noticed that when trying to ping, that takes the same amount of time to initialize.

Has anyone else noticed this issue and have any suggestions?

Thanks,
Mike
0
msheppard74
Asked:
msheppard74
  • 4
  • 2
1 Solution
 
dj_relentlessCommented:
That's normal on the first run when using application pools. Theres a good reason for it but I don't know the technical details.
0
 
msheppard74Author Commented:
Well, I know that everything takes a little bit to initialize with application pools, but this doesn't even appear to be the same thing. The website isn't even responding to the request at first...the browser just sits waiting for an ACK from the server.

If it was an Application Pool issue, PING-ing wouldn't do the same thing. It seems to be a network or data link layer issue to me.
0
 
dj_relentlessCommented:
It's an asp.net website right? It could be something else all together, I'm just saying that by default when you first startup an iis site it will take a while to respond to the first request while it initializes. If you think it's a network layer issue then it should be happening irrelevant of having IIS started or not right?
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
msheppard74Author Commented:
That is correct. This happens if you open a browser ON the server and go to say espn.com or something, the browser just sits there and takes a long time and then finally makes a connection after 12 or more seconds. After that you can navigate that website easily, you can even close the browser open it back up and load up espn right away. However, if you wait like 20 minutes that initial delay happens again. This same thing happens when you try to get to the site our server is hosting. This will happen regardless of how long IIS has been up for.

Then keep in mind that PING acts in the same manner, which is what makes me think it's something to do with the network and maybe even transport layer. It's like it has a hard time creating sockets, but after a while finally does...it's definitely weird.
0
 
msheppard74Author Commented:
And yes, I can shut down IIS and try to go to some website from that server...same delay is there.
0
 
msheppard74Author Commented:
I rebuilt the server and that took care of the problem.
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

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