|
Home > Archive > BizTalk Server Orchestration > July 2005 > DeliveryFailureException handling
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 |
DeliveryFailureException handling
|
|
| Michel Prévost 2005-07-12, 5:51 pm |
| Hello All
I have an orchestration in which I have to be notified if the Send failed,
and retry. I have to handle this in my orchestration because I have to do
some special actions in case of failure. For instance, I try 3 times in a
row. If the 3 retries fail, I suspend the orchestration and send a message
so the problem is handled ASAP. Once this is done, the operator can resume
the orchestration from HAT and everything is good.
All this works like a charm, except for one thing: the send port instances
stay in the "suspended (resumable)" status. Any idea how I can get rid of
those from within the orchestration, or a way to make a send port terminate
if it fails?
Thank you
Michel
| |
| Stephen W. Thomas 2005-07-13, 6:00 pm |
| Hello.
I do not know a way to suppress the error messages or automatically
terminate the service instance. Although, I think having that level of
control when using Delivery Notification would be a great feature.
If you wanted to have the Orchestration terminate the message it can be done
using WMI inside a helper class.
This post (http://geekswithblogs.net/bloesgen/...0/30/14104.aspx)
queries for suspended message using a stored procedure. I would guess this
could be modified to terminate them as well.
Hope this helps.
Stephen W. Thomas
http://www.biztalkgurus.com
"Michel Prévost" wrote:
> Hello All
>
> I have an orchestration in which I have to be notified if the Send failed,
> and retry. I have to handle this in my orchestration because I have to do
> some special actions in case of failure. For instance, I try 3 times in a
> row. If the 3 retries fail, I suspend the orchestration and send a message
> so the problem is handled ASAP. Once this is done, the operator can resume
> the orchestration from HAT and everything is good.
>
> All this works like a charm, except for one thing: the send port instances
> stay in the "suspended (resumable)" status. Any idea how I can get rid of
> those from within the orchestration, or a way to make a send port terminate
> if it fails?
>
> Thank you
> Michel
>
>
>
| |
| Michel Prévost 2005-07-14, 5:51 pm |
| Hello Stephen
That does not quite addresses my concern. I need a way to figure out the
send port and terminate it. But this is a good starting point though :-)
Thank you
"Stephen W. Thomas" <StephenWThomas@discussions.microsoft.com> wrote in
message news:F85C9078-0BE6-4F2E-9B50-FD116769BDAB@microsoft.com...[vbcol=seagreen]
> Hello.
>
> I do not know a way to suppress the error messages or automatically
> terminate the service instance. Although, I think having that level of
> control when using Delivery Notification would be a great feature.
>
> If you wanted to have the Orchestration terminate the message it can be
> done
> using WMI inside a helper class.
> This post
> (http://geekswithblogs.net/bloesgen/...0/30/14104.aspx)
> queries for suspended message using a stored procedure. I would guess
> this
> could be modified to terminate them as well.
>
> Hope this helps.
>
> Stephen W. Thomas
> http://www.biztalkgurus.com
>
>
> "Michel Prévost" wrote:
>
|
|
|
|
|