I have a front end running an ASP.NET web service client and a middle tier
running an ASP.NET web service.

If I restart the web service on the middle tier (e.g. update a configuration
file), it takes way too long for the front end to recover. It just queues up
requests (and start dropping them with web service timeout errors) for a long
time (around 5 minutes, or more).

It seems that it's a web service client problem, because I can use a browse
on any of the front end boxes to invoke the web service. It's just the
ASP.NET client takes way too long to recover.

Has anybody had such a problem before? Is there a workaround that makes the
web service client recovers faster?

Thanks