|
Home > Archive > BizTalk Server General > May 2005 > Reprocessing suspended messages?
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 |
Reprocessing suspended messages?
|
|
|
| Hi all,
In our BTS application, Class dlls which are called by Orchestration
connect to Oracle database and completes the transactions. In case of Oracle
database connection failures these class modules makes four attemps and then
throw exceptions. Then messages goes into suspended, (not resumable) state.
Is there any way that we can process these messages again at a point
where they failed. This is very important in Production environment where
reprocessing from start is not possible.
Thanks,
RR.
| |
| Scott Colestock 2005-05-14, 1:16 pm |
| One option is to have your orchestration catch the exceptions, and then
suspend (via the suspend shape).
Place the whole process in a loop (that exits when success=true), so then
when you resume (via HAT or external tool), you are retrying the operation
that failed.
Does that make sense?
Scott Colestock
www.traceofthought.net
"RR" <RR@discussions.microsoft.com> wrote in message
news:49726186-0AF9-4320-AF94-180DBF81135F@microsoft.com...
> Hi all,
>
> In our BTS application, Class dlls which are called by Orchestration
> connect to Oracle database and completes the transactions. In case of
> Oracle
> database connection failures these class modules makes four attemps and
> then
> throw exceptions. Then messages goes into suspended, (not resumable)
> state.
> Is there any way that we can process these messages again at a point
> where they failed. This is very important in Production environment where
> reprocessing from start is not possible.
>
> Thanks,
> RR.
| |
|
| Scott,
Thanks for reply.
This involves changes to Orchestration. As the application is already in
production, may be we should try this in the new releases.
Can you please give more info on "resume(via HAT or external tool)" or links
where I can understand more.
Also please let me know if any other solutions possible to reprocess
suspended messages?
Thanks,
RR.
"Scott Colestock" wrote:
> One option is to have your orchestration catch the exceptions, and then
> suspend (via the suspend shape).
> Place the whole process in a loop (that exits when success=true), so then
> when you resume (via HAT or external tool), you are retrying the operation
> that failed.
>
> Does that make sense?
>
> Scott Colestock
> www.traceofthought.net
>
>
>
> "RR" <RR@discussions.microsoft.com> wrote in message
> news:49726186-0AF9-4320-AF94-180DBF81135F@microsoft.com...
>
>
>
| |
| Scott Colestock 2005-05-14, 1:16 pm |
| Orchestrations that suspend "intentionally" via the suspend shape can be
resumed in HAT by right-clicking and selecting resume in the
Operations-Services view. You can also write WMI scripts that would
selectively find orchestrations that were suspended and (based on some
criteria) cause them to resume.
Yes, you will have to change the orchestration to get this type of
"reprocess-ability" in the manner described here.
An alternative is to ensure that your orchestration design hasn't left any
work partially completed so that it is safe to resubmit the activating
message (which, with the right tracking enabled, can be recovered externally
through WMI.)
Scott Colestock
www.traceofthought.net
"RR" <RR@discussions.microsoft.com> wrote in message
news:623A4136-3B6A-4DE2-9F82-04287901C2FD@microsoft.com...[vbcol=seagreen]
> Scott,
>
> Thanks for reply.
> This involves changes to Orchestration. As the application is already in
> production, may be we should try this in the new releases.
> Can you please give more info on "resume(via HAT or external tool)" or
> links
> where I can understand more.
> Also please let me know if any other solutions possible to reprocess
> suspended messages?
>
> Thanks,
> RR.
>
>
> "Scott Colestock" wrote:
>
|
|
|
|
|