Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Handling PersistenceException in Direct bound orchestrations
- This topic has 0 replies, 1 voice, and was last updated 9 years, 10 months ago by
community-content.
-
AuthorPosts
-
-
February 28, 2008 at 6:46 AM #19002
Hi,
I am using 2 orchestrations Orch A and Orch B which commute using a direct bound port ( using Partner port). Orch A initiates the process and Orch B sends back the response to Orch A . The messages are routed using correlation since the response is asynchronous, The problem is that if Orch A is not running and Orch B try to send a response , then there will be “PersistenceException” thrown inside Orch B. Eventhough the exception block capture this exception and the Orch B completes, some how I am seeing a couple suspende (non resumable) instances of Orch B under Biztalk admin console. Why this happens, is there any way to avoid this ? Please help me to resolve this issue..
Here is the exception received in Orch B.
occurred.
Service Name: bt_Orchestrator.Error_Notify
Service Id: b3e358c5-c0f2-0042-356b-cf9d55bb54af
Instance Id: 0e288c5f-d70c-456f-b9de-33c76c9045b4
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.BizTalk.XLANGs.BTXEngine.BTXXlangStore.ScheduleComplete(Boolean terminate)
at Microsoft.BizTalk.XLANGs.BTXEngine.BTXService.ScheduleComplete(Context ctx, Boolean finalPersisting, Boolean terminate)
at Microsoft.XLANGs.Core.Service.Persist(Boolean dehydrate, Context ctx, Boolean idleRequired, Boolean finalPersist, Boolean bypassCommit, Boolean terminate)
at Microsoft.XLANGs.Core.TransactionalContext.OnCommit()
at Microsoft.XLANGs.Core.LongRunningTransaction.OnCommit()
at bt_Orchestrator.Error_Notify.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 720af195-0c41-4892-9f64-0f7d12ef5130 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
Sam
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.