biztalk - 挂起的编排服务实例在 Resume 后重新抛出相同的意外异常

Question

当我尝试恢复挂起(可恢复)编排实例时，出现以下错误。

场景:请求通过 DB2 静态请求 - 响应端口，但由于访问权限被拒绝而失败。我可以在管理控制台中看到两个暂停的实例，一个与端口相关，另一个与编排相关。修复凭据后，暂停的端口实例恢复，但编排实例一直失败。

Uncaught exception (see the 'inner exception' below) has suspended an instance of service 'Orchestration name'.
The service instance will remain suspended until administratively resumed or terminated. 
If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.
InstanceId: ca927086-465d-40e8-93fe-c3a0e4c161f7
Shape name: 
ShapeId: 
Exception thrown from: segment -1, progress -1
Inner exception: An error occurred while processing the message, refer to the details section for more information 
Message ID: {96B72521-9833-48EF-BB2F-4A2E2265D697}
Instance ID: {F6FBC912-C9DC-489C-87F3-103FA1273FDC}
Error Description: The user does not have the authority to access the host resource. Check your authentication credentials or contact your system administrator. SQLSTATE: HY000, SQLCODE: -1000


Exception type: XlangSoapException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void VerifyTransport(Microsoft.XLANGs.Core.Envelope, Int32, Microsoft.XLANGs.Core.Context)
The following is a stack trace that identifies the location where the exception occured
at Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.VerifyTransport(Envelope env, Int32 operationId, Context ctx)
at Microsoft.XLANGs.Core.Subscription.Receive(Segment s, Context ctx, Envelope& env, Boolean topOnly)
at Microsoft.XLANGs.Core.PortBase.GetMessageIdForSubscription(Subscription subscription, Segment currentSegment, Context cxt, Envelope& env, CachedObject location)
at Microsoft.XLANGs.Core.PortBase.GetMessageId(Subscription subscription, Segment currentSegment, Context cxt, Envelope& env, CachedObject location)
at (StopConditions stopOn)
at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

有什么想法可以解决这个问题吗？

使用示例创建上述场景:

1. 转到 BizTalk示例/业务流程/consumeWebservice文件夹，安装ConsumeWebService 应用程序和将 POWebservice 发布到 IIS。
2. 更改 IIS 目录安全性POWebservice 的权限，删除匿名或任何其他访问。
3. 现在放下您将看到的消息由于 HTTP 而暂停的消息状态 401:访问被拒绝，然后给访问 POWebservice匿名或 Windows。
4. 然后继续挂起的实例，一个将消失但是另一个(编排)一个不会。

Answer 1

编排会继续失败并抛出异常，因为挂起时，最后的持久点是接收到异常。这意味着编排将重新启动(恢复时)并重新抛出异常。

本文讨论了将编排状态持久保存到数据库的一些要点:http://blogs.msdn.com/b/sanket/archive/2006/11/12/understanding-persistence-points-in-biztalk-orchestration.aspx

正如 Richard Seroter 所讨论的 here，您可以在编排设计中在某种程度上操纵它, 但通常你最好使用 failed message routing ，使您能够处理失败的消息，并终止失败的编排实例。