恢复挂起的消息或挂起的服务实例之间的区别
我们遇到了一堆挂起的服务实例（比如 100 个）。我们还注意到有超过 100 条（相关的）挂起消息（大部分带有 NACK）。
从挂起的服务实例恢复或从挂起的消息恢复有什么区别？
We encounter a bunch of suspended service instances (like 100). Also we notice that there are more than 100 (related) suspended messages (mostly with NACKs).
What is the difference then to resume from a suspended service instance or to resume from a suspended message ?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
服务实例处理消息。
BizTalk 将服务分解为服务类，例如路由故障、隔离适配器和消息传递。尽管消息与服务相关联，但这些服务与消息不同。当 BizTalk 中出现故障时，通常消息和服务实例都会在 BizTalk 管理控制台中显示为已挂起。如果您查看服务的详细信息，您将看到它包含一个包含消息的选项卡。
在此上下文中，消息是服务实例的属性。该服务尝试对该消息执行某些操作，但失败了。因此，恢复操作（服务实例）是有意义的，这将利用数据（消息）。尝试执行诸如恢复 NACK（消息）之类的操作是没有意义的；相反，您应该恢复服务实例。 NACK 可以帮助您找出问题所在，但如果在解决问题并恢复服务实例后它没有消失，那么通常可以安全地清除它。
Service instances process messages.
BizTalk breaks up services into Service Classes, such as Routing Failure, Isolated Adapter, and Messaging. Those services are distinct from the messages, though the messages are associated with a service. When something fails in BizTalk, typically both a message and a service instance show up in the BizTalk Administration Console as being suspended. If you view the details of the service, then you'll see that it contains a tab with the message(s).
In this context, the message is a property of the service instance. The service was trying to do something with the message and failed. Thus is makes sense to resume the action (service instance), which will make use of the data (message). It doesn't make sense to try and do something like resume a NACK (a message); instead, you should resume the service instance. The NACK can help you find out what went wrong, but if it doesn't go away after resolving the problem and resuming the service instance, then it typically can be safely cleared out.