[BTS]10008错误如何处理？
错误提示如下
Event Type: Error
Event Source: XLANG/s
Event Category: None
Event ID: 10008
Date: 2/21/2008
Time: 9:45:27 PM
User: N/A
Computer: LABS
Description:
Uncaught exception (see the 'inner exception' below) has suspended an instance of service 'EIAC.OA.NotificationSystem.Orchestrations.Main(a44769cf-20b3-668b-e434-e1b03b6f84c2)'.
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: ea3c1bab-8383-4bb5-993a-85a7bf05dc66
Shape name: RequestCreateEMailLog
ShapeId: d76938c8-3bb5-408a-9ac5-e0e762bb489b
Exception thrown from: segment 1, progress 37
Inner exception: Exception occurred when persisting state to the database.
Exception type: PersistenceException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void Commit()
The following is a stack trace that identifies the location where the exception occured
at Microsoft.BizTalk.XLANGs.BTXEngine.BTXXlangStore.Commit()
at Microsoft.XLANGs.Core.Service.Persist(Boolean dehydrate, Context ctx, Boolean idleRequired, Boolean finalPersist, Boolean bypassCommit, Boolean terminate)
at Microsoft.XLANGs.Core.ServiceContext.PendingCommit(Boolean ignore, XMessage msg)
at Microsoft.XLANGs.Core.ExceptionHandlingContext.PendingCommit(Boolean ignoreCommit, XMessage msg)
at Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.SendMessage(Int32 iOperation, XLANGMessage msg, Correlation[] initCorrelations, Correlation[] followCorrelations, SubscriptionWrapper& subscriptionWrapper, Context cxt, Segment seg, ActivityFlags flags)
at Microsoft.XLANGs.Core.PortBase.SendMessage(Int32 iOperation, XLANGMessage msg, Correlation[] initCorrelations, Correlation[] followCorrelations, SubscriptionWrapper& subscriptionWrapper, Context cxt, Segment seg)
at EIAC.OA.NotificationSystem.Orchestrations.Main.segment1(StopConditions stopOn)
at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)
Additional error information:
A batch item failed persistence Item-ID 7a083b87-980c-4888-8cbc-35b14cef2bc8 OperationType MAIO_CommitBatch Status -1061151998 ErrorInfo The published message could not be routed because no subscribers were found. .
Exception type: PersistenceItemException
Additional error information:
Failed to publish (send) a message in the batch. This is usually because there is no one expecting to receive this message. The error was The published message could not be routed because no subscribers were found. with status -1061151998.
Exception type: PublishMessageException
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
正在研究它出错的原因
问题找到了，从上面的错误信息中可以看到，是由于没有消息的订阅者，这是为什么呢。原来，开发中错误的使用了Direct方式配置流程中的SendPort
我真是太大意了，这也能搞错。(当时看也没看就这么选上了，配置部署时，也没发现少了一个绑定端口)
Direct绑定是Orchestration之间，通过这种把流程中的send / receive进行直接绑定，实现消息在Orchestration中的传递。
把端口重新绑定了一下，问题解决了。
自勉：吃一堑，长一智不。
