|
Home > Archive > BizTalk Server Orchestration > January 2005 > Suspended (not resumable)
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 |
Suspended (not resumable)
|
|
| John Lee 2005-01-27, 8:47 pm |
| Hi,
In BizTalk Server 2000/2002, when there is something wrong with the
message/process the message is kicked back to suspended queue - we can
always re-submitted when the problem gets fixed.
In BizTalk Server 2004, from the HAT, I saw lots of Suspended (Not
Resumable) entry, what do I need to do to make all suspended message
resumable? What's the decision factor for BTS 2004 to define a failure is
resumable or not? It seems to me BTS 2004 has poor document tracking feature
and poor failure recovery feature.
Thanks very much!
John
| |
| WenJun Zhang[msft] 2005-01-28, 7:51 am |
| Hi John,
Here is the explanation in biztalk document about the "not resumable"
status.
You cannot use HAT to recover all other failures, for example, a
disassembler failure. However, you can use the Operations view in HAT
to find and save the message body to a file for further diagnostic or
manual recovery. In the case of routing failure, a Routing Failure
Report automatically generates and shows in HAT as a message with
"Suspended (not resumable)" as Service Status and "routing Failure
Report" as Service Class.
I wonder what the detailed error info you got in the event log was?
See if it just applies to the case above.
Thanks.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
| |
| John Lee 2005-01-28, 5:49 pm |
| Thanks for your reply, WenJun!
I was referring this in general - not specific error I had. I have a lots of
the "suspended (not resumable)" ...
Let's say, if in orchestration an expression shape calls a .net component
method, an exception is thrown in the .net component when accessing
database - i.e. timeout or deadlock, then the instance of orchestration is
suspended and not resumable. It would be nice that in this scenario we could
use the HAT to resume the orchestration w/o save the message and resubmit
that document to kick off the orchestration again.
Thanks!
John
""WenJun Zhang[msft]"" <v-wzhang@online.microsoft.com> wrote in message
news:Zqkqo%23SBFHA.1392@cpmsftngxa10.phx.gbl...
> Hi John,
>
> Here is the explanation in biztalk document about the "not resumable"
> status.
>
> You cannot use HAT to recover all other failures, for example, a
> disassembler failure. However, you can use the Operations view in HAT
> to find and save the message body to a file for further diagnostic or
> manual recovery. In the case of routing failure, a Routing Failure
> Report automatically generates and shows in HAT as a message with
> "Suspended (not resumable)" as Service Status and "routing Failure
> Report" as Service Class.
>
> I wonder what the detailed error info you got in the event log was?
> See if it just applies to the case above.
>
> 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-01-31, 7:46 am |
| Hi John,
I agree this may be a good feature request. You can submit it to our
MS Wish at your convenience.
Actually we do provide MSBTS_MessageInstance and
MSBTS_ServiceInstance WMI classes, which can help on such kind of
automation scenarios with a little programming.
We can enumerate messages in the message box using
MSBTS_MessageInstance WMI class, and look at two fields below figure
out state of the message:
[read, Description("This property contains state of the service
instance this message belongs to."),
ValueMap{"1", "2", "4", "8", "16", "32", "64"}, Values {"Ready
to run", "Active", "Suspended (resumable)", "Dehydrated", "Completed
with discarded messages", "Suspended (not resumable)", "In
breakpoint"} ]
uint32 ServiceInstanceStatus;
[read, Description("This property contains information about
how message is referenced by a service."),
ValueMap{"1", "2", "4", "8"}, Values {"Delivered, not
consumed", "Consumed", "Suspended", "Abandoned"} ]
uint32 ReferenceType;
According to a today's post, looks like somebody has implemented a
similiar component. FYI:
http://martijnh.blogspot.com/2004/0...nded-queue-list
ener.html
Thanks.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
|
|
|
|
|