|
Home > Archive > BizTalk Server Orchestration > October 2005 > Catching Timeout Exception in a long-running scope
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Catching Timeout Exception in a long-running scope
|
|
|
| I have parallel-receive convoy orchestration and I'm trying to scope a
section of the orchestration. I have the scope set up as long-running, and
am successfully timing out the orchestration, but when I try to catch the
timeout exception, the actions in the CatchException shape are not executing.
I am catching Microsoft.XLANGs.Basetypes.TimeoutException (because that's
the only timeout exception type I can find), but the suspended service
instances show exceptions of Microsoft.XLANGs.Core.TimeoutException. How can
I catch this type of exception?
--
Thanks;
cori
| |
|
| Update: I've also tried it by catching a general exception and still the
actions in the catch exception shape do not execute.
What am I missing?
--
Thanks;
cori
"cori" wrote:
> I have parallel-receive convoy orchestration and I'm trying to scope a
> section of the orchestration. I have the scope set up as long-running, and
> am successfully timing out the orchestration, but when I try to catch the
> timeout exception, the actions in the CatchException shape are not executing.
>
> I am catching Microsoft.XLANGs.Basetypes.TimeoutException (because that's
> the only timeout exception type I can find), but the suspended service
> instances show exceptions of Microsoft.XLANGs.Core.TimeoutException. How can
> I catch this type of exception?
> --
> Thanks;
> cori
| |
| WenJun Zhang[msft] 2005-10-07, 7:48 am |
| Hi Cori,
Just a common idea to achieve this kind of scenarios:
You may consider os using parallel branch, a delay shape to decide if
file was received after the delay. If it wasn't, throw an exception
or just end if no error is required.
Thanks.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
| |
|
| I can certainly try that; what properties can I check in my expression to see
if the message I'm looking for has been received?
On a related note; even when I timeout my orchestration, the webservice
that's acting as its front-end still times out at the limit set in the web
application. Is there a way to have the webservice fail sooner when the
orchestration times out? I can't adjust the timeout setting on the web
application because it contains a webservice that requires the longer time
out.
Thanks!
--
Thanks;
cori
""WenJun Zhang[msft]"" wrote:
> Hi Cori,
>
> Just a common idea to achieve this kind of scenarios:
>
> You may consider os using parallel branch, a delay shape to decide if
> file was received after the delay. If it wasn't, throw an exception
> or just end if no error is required.
>
> Thanks.
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Partner Support
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
| |
| WenJun Zhang[msft] 2005-10-10, 7:51 am |
| Hi Cori,
You don't need to query any properties. Commonly this is approached
by using a listen shape inside a loop, with the receive port on one
side and a delay shape on the other, and if the delay expires before
a message arrives the instance then terminates.
For the second issue, I am not aware of any way to inform the web
service from biztalk client side. However if the response message is
finally sent out from the web service, you may run into following
issue.
FIX: Messages are processed and delivered even if the orchestration
instance finishes with a status of "Completed with discarded
messages" in BizTalk Server 2004
http://support.microsoft.com/defaul...kb;en-us;892405
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
| |
|
| OK, I'll see if I can make that work in my situation.
--
Thanks;
cori
""WenJun Zhang[msft]"" wrote:
> Hi Cori,
>
> You don't need to query any properties. Commonly this is approached
> by using a listen shape inside a loop, with the receive port on one
> side and a delay shape on the other, and if the delay expires before
> a message arrives the instance then terminates.
>
> For the second issue, I am not aware of any way to inform the web
> service from biztalk client side. However if the response message is
> finally sent out from the web service, you may run into following
> issue.
>
> FIX: Messages are processed and delivered even if the orchestration
> instance finishes with a status of "Completed with discarded
> messages" in BizTalk Server 2004
> http://support.microsoft.com/defaul...kb;en-us;892405
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Partner Support
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
| |
| WenJun Zhang[msft] 2005-10-12, 6:12 pm |
| Cori,
Please feel free to post here again if you meet any problem.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
|
|
|
|
|