I'm building a simple (for now) WCF service with BizTalk. It calls a stored procedure through the WCF-SQL adapter, and returns the result set (through a map). It is published with the WCF wizard using "schemas as WCF service". It is up and running and works fine. What I am trying to do is fix the behavior when something is wrong, specifically when the SQL server (containing the strored procedure) is unavailable. I want it to return a fault message (a generic message is fine, just so the consumer know that it failed), but the service times out instead.
On the Receive location, I turned on "Suspend request message on failure" and "Include exception details in faults". I also reduced the "Open timeout","Send rimeout", and "Close timeout" to 10 seconds. On the WCF-SQL send port I reduced the Retry count to 0. The orchestration has an exception handler, and it is catching the ConnectionException (I'm writing it to the log) and sending it to the fault section of the orchestration's port.
I also tried a "no orchestration" solution, and it worked the same way, other than logging the exception.
I just want the service to fail quickly instead of leaving the caller hanging. What am I missing?