Hi,
The Circuit Breaker pattern, from the book Release It!, protects a service from requests while it is failing (or recovering). The net.msmq binding used with transactions give us nice retry and poison message capabilities. But I am missing the implementation of such a "Circuit breaker" pattern. A service is put under even heavier load by retries while it is already in a failure condition (like DB connectivity issues causing loads of blocked threads etc.).
Anyone knows about a behavior extension or similar that explicitly closes the service host when defined failure thresholds have been exceeded?
EDITED:
Or, even if there is no automation: How I can manually "disable" a net.msmq bound endpoint in a IIS hosted web application? Shutting down or recycling the whole app pool is not an option as further critical services are hosted by the same application.
Cheers, Alex