I have several places in my orchestration where I receive an HTTP (or SMTP)
request and send a response. In some cases the response is delayed. If the
response is delayed long enough, the Send of the response fails because
the
IIS session of the BTSHttpReceive listener or web service has timed out.
Then my orchestration suspends. I want to avoid this suspension.
I thought I would compare the current time with the timestamp of the
original request and if too much time has elapsed, then don't try to send
a
response. This seemed like a good solution because it avoids the error
condition altogether. Unfortunately the compiler won't let me do this
because it results, at least potentially, in a request-response without a
response. But in this case, a request-response without a response is
exactly
what I want. But apparently in BizTalk it's verboten.
Is this a common problem and is there a common, easily implemented
solution?
I'm going to start to look at putting a scope and catch around the Send to
see if I can catch the exception that occurs when I attempt to send the
response.
But I'm looking for any other suggestions.
Thanks,
Zoe
|
