Hello

I have created an orchestration that

1) Excecutes a stored proc and returns a result set
2) Sends the results to the Business Rules engine for validation

As this orchestration is being published as a web service how does one
return a message to the calling app if there is a problem with the stored
proc or within the rules engine. At the moment all errors go the the
application log and the calling app eventually times out. Is there any good
doco on Exception Handling  within orchestrations ?

Regards

Tim

[ Post a follow-up to this message ]

Hi Tim,

What I suspect is happening is your orchestration is suspending, and the web
service response is never getting sent to the client. You should try to
handle all exceptions (using a catch block), and make sure you return
someting to the client whatever happenes.

There's an article on exception handling here:
http://weblogs.asp.net/jan/archive/...3/22/93981.aspx

And one on returning SOAP faults here:
http://thearchhacker.blogspot.com/2...er_archive.html

One point if you are using the SQL adapter, the default port settings has a
retry count of 3, and retry interval of 5 minutes. This means if there is an
error raised by the SPROC, it's going to be 20 minutes before you web servic
e
client gats the return message. This latencey may be OK in messaging systems
,
but it's not good for web sevices.

Regards,

Alan

"TimG" wrote:

> Hello
>
> I have created an orchestration that
>
> 1) Excecutes a stored proc and returns a result set
> 2) Sends the results to the Business Rules engine for validation
>
> As this orchestration is being published as a web service how does one
> return a message to the calling app if there is a problem with the stored
> proc or within the rules engine. At the moment all errors go the the
> application log and the calling app eventually times out. Is there any goo
d
> doco on Exception Handling  within orchestrations ?
>
> Regards
>
> Tim
>

[ Post a follow-up to this message ]