meta user
network profile
| bio | website | redwerb.com |
|---|---|---|
| location | United States | |
| age | 41 | |
| visits | member for | 3 years, 8 months |
| seen | Feb 26 at 19:04 | |
| stats | profile views | 6 |
|
Jan 15 |
accepted | How do I change the Web Farm Framework (WFF) controller server? |
|
Jan 10 |
revised |
How do I change the Web Farm Framework (WFF) controller server? Added notes about restarting controller server. |
|
Jan 9 |
revised |
How do I change the Web Farm Framework (WFF) controller server? Added details on copying existing web farm from applicationHosts.config. |
|
Jan 9 |
answered | How do I change the Web Farm Framework (WFF) controller server? |
|
Jan 9 |
revised |
How do I change the Web Farm Framework (WFF) controller server? Figured out the proper terminology and updated my question to reflect it. |
|
Jan 9 |
asked | How do I change the Web Farm Framework (WFF) controller server? |
|
Nov 8 |
awarded | Tumbleweed |
|
Nov 1 |
asked | Allow different headers on different servers using WFF |
|
Aug 30 |
awarded | Scholar |
|
Aug 30 |
accepted | Microsoft Web Farm Framework failing due to lack of hard drive space |
|
Jun 8 |
comment |
How do I determine why IIS takes 60+ seconds to fail? Nothing but Timer_ConnectionIdle for today. My understanding is that this is normal. |
|
Jun 8 |
revised |
How do I determine why IIS takes 60+ seconds to fail? added 18 characters in body |
|
Jun 8 |
comment |
How do I determine why IIS takes 60+ seconds to fail? I rewrote the question. It seems that people were focusing on the wrong thing. Hopefully the rewrite will clear up the confusion. |
|
Jun 8 |
awarded | Editor |
|
Jun 8 |
revised |
How do I determine why IIS takes 60+ seconds to fail? Rewrote the question to be clearer as to what I'm trying to get.; added 25 characters in body |
|
Jun 8 |
comment |
How do I determine why IIS takes 60+ seconds to fail? My IIS logs don't show any errors, they just show the GETs and POSTs. The event viewer just shows the error that was thrown (the only thing the code does is throws an exception). I'm sure it's not the app since this same app doesn't have any problems showing errors when run in the test environment (not on the domain). Also I see the same problem in other apps that I didn't write. Really what I'm looking for is some kind of tool to help me diagnose a domain or network issue. |
|
Jun 8 |
comment |
How do I determine why IIS takes 60+ seconds to fail? I'm really just looking for a way to diagnose a domain or network error (there's got to be something that shows system errors). The application works just fine when there isn't an error, I've already disabled Elmah which was the only thing in my code that handled errors, and this problem does not show up in our test environment (same exact code). The test environment is not on the domain. This same pause happens in other applications that I didn't write. This is a distinct pause of a specific duration. There does not seem to be any excessive processor, disk, or network activity. |
|
Jun 8 |
comment |
How do I determine why IIS takes 60+ seconds to fail? It's on my local machine using my machine name to connect to it. Using localhost and 127.0.0.1 did not do anything to help. I agree that it doesn't seem like a network issue other than the length of time for the pause is similar to a network connection failing. I don't know of any other reason why something would pause like it does. Personally I think it's a problem on our domain, I've heard of other people complaining about performance issues, but I need to figure out what is causing it (it's a small office without a full time sys admin). |
|
Jun 8 |
comment |
How do I determine why IIS takes 60+ seconds to fail? The pause is when there is an error (if there isn't an error it works just fine). It shouldn't take 60+ seconds to render an error. It certainly has never taken that long on any other development machine I've used including my personal machine which has a very similar configuration other than it isn't connected to my works domain. |
|
Jun 8 |
asked | How do I determine why IIS takes 60+ seconds to fail? |
