Quantcast
Channel: General
Viewing all articles
Browse latest Browse all 7363

IIS Application Request Routing Health Check failures

$
0
0
So I'm having a problem with Application Request routing where servers are being marked as unhealthy when they aren't. My configuration routes to three separate boxes with http servers running on port 8080 (not IIS -- Jetty). The Interval is set at 30 s and the Time-out is set at 30 s. Acceptable Status codes are 200-399 In eventvwr, all I see is.... Server 'name' in server farm 'farmName' is being marked unhealthy due to unknown health check failure. There's not enough information for me to see what's causing the failure. I've bumped the timeout on the health check up to 120 s. Doesn't fix it. Sometimes the health checks succeed, and sometimes they fail; there's no rhyme or reason to telling when they will fail. I've tried checking both text files and images being served with the same result. I set up Faied Request Tracing -- I didn't get anything out of the logs, but perhaps someone else will. I'm happy to provide them to whoever is willing to take a look. At the end of the day, my configuration works -- I hit the URL on the main server and it routes the request successfully to one of the delegated boxes in the server farm. But with boxes being marked as unhealthy in this "willy nilly" kind of fashion, I don't know that I'll be able to use ARR. I need to be able to tell which boxes are actually Healthy, and I'm not able to determine that right now. Has anyone run into this before? Can you point me in the right direction? I'm happy to provide any additional details to solve this issue...

Viewing all articles
Browse latest Browse all 7363

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>