|
Home > Archive > BizTalk Server Orchestration > July 2005 > Terminate a correlated Biztalk instance
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 |
Terminate a correlated Biztalk instance
|
|
| Cindy Liu 2005-07-26, 8:47 pm |
| Hi Everyone,
I have an orchestration that uses 2 types of schema and is correlated by the
MessageType. This means there are 2 instances of the orchestration running.
One of instances will determine when these 2 instances should be terminated.
The instance who decides the termination can terminate itself very easily.
But it is very hard for me to tell the other instance to terminate.
I tried to create the similar message used by the other instance so that it
has the same message type for the correlation to get in its instance. Then I
created one way Direct send port and sent that message to this port. The type
of Direct binding was "Routing between ports will be defined by filter
expressions on incoming messages in the Message Box database." I added
MessageType filter on the activation Receive shape of the instance that is
hard for me to terminate. Then ran my orchestration. I got the following
error. Does anyone know how to send messages between orchestration instances?
Is there any sample code on how to use Direct binding?
Uncaught exception terminated service
Invensys.Shell.IP.IPEngine.IPOrchestration(28b56d76-f717-10fc-cfd9-141013200de5), instance 7b33d073-fbee-4cd4-9391-3c76b09bc692
Exception occurred when persisting state to the database.
Exception type: PersistenceException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void Commit()
Help Link:
Additional error information:
A batch item failed persistence Item-ID 759069ec-dab9-4193-8d30-61f414e1b6c2
OperationType MAIO_CommitBatch Status -1061151998 ErrorInfo The published
message could not be routed because no subscribers were found. Please use the
Health and Activity Monitoring (HAT) tool to diagnose this situation. .
Exception type: PersistenceItemException
Source:
Target Site:
Help Link:
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.
Please use the Health and Activity Monitoring (HAT) tool to diagnose this
situation. with status -1061151998.
Exception type: PublishMessageException
Source:
Target Site:
Help Link:
Additional error information:
Exception occurred when persisting state to the database.
Exception type: PersistenceException
Source: Microsoft.XLANGs.BizTalk.Engine
Target Site: Void
Commit(Microsoft.BizTalk.Agent.Interop.IBTMessageBatchEx[],
Microsoft.XLANGs.Core.Segment,
Microsoft.BizTalk.Agent.Interop.IBTOperationStatus ByRef)
Help Link:
Additional error information:
A batch item failed persistence Item-ID 759069ec-dab9-4193-8d30-61f414e1b6c2
OperationType MAIO_CommitBatch Status -1061151998 ErrorInfo The published
message could not be routed because no subscribers were found. Please use the
Health and Activity Monitoring (HAT) tool to diagnose this situation. .
Exception type: PersistenceItemException
Source:
Target Site:
Help Link:
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.
Please use the Health and Activity Monitoring (HAT) tool to diagnose this
situation. with status -1061151998.
Exception type: PublishMessageException
Source:
Target Site:
Help Link:
Additional error information:
Thanks in advance!!!!!
Cindy
| |
| Stephen W. Thomas 2005-07-27, 2:48 am |
| Hello.
This is a great resource: http://geekswithblogs.net/cyoung/articles/19546.aspx
I think the problem is long the lines of when you send the message the
message type field is not promoted. If I remember correctly, I think Direct
Binding demotes message type thinking it would match unwanted subscription.
You might have to create your own custom property to route on instead. Then,
the key would be to get that value promoted.
Anyway, take a look at his article. That should help you out.
Stephen W. Thomas
http://www.biztalkgurus.com
"Cindy Liu" wrote:
> Hi Everyone,
>
> I have an orchestration that uses 2 types of schema and is correlated by the
> MessageType. This means there are 2 instances of the orchestration running.
> One of instances will determine when these 2 instances should be terminated.
> The instance who decides the termination can terminate itself very easily.
> But it is very hard for me to tell the other instance to terminate.
>
> I tried to create the similar message used by the other instance so that it
> has the same message type for the correlation to get in its instance. Then I
> created one way Direct send port and sent that message to this port. The type
> of Direct binding was "Routing between ports will be defined by filter
> expressions on incoming messages in the Message Box database." I added
> MessageType filter on the activation Receive shape of the instance that is
> hard for me to terminate. Then ran my orchestration. I got the following
> error. Does anyone know how to send messages between orchestration instances?
> Is there any sample code on how to use Direct binding?
>
> Uncaught exception terminated service
> Invensys.Shell.IP.IPEngine.IPOrchestration(28b56d76-f717-10fc-cfd9-141013200de5), instance 7b33d073-fbee-4cd4-9391-3c76b09bc692
>
> Exception occurred when persisting state to the database.
>
> Exception type: PersistenceException
> Source: Microsoft.XLANGs.BizTalk.Engine
> Target Site: Void Commit()
> Help Link:
> Additional error information:
>
> A batch item failed persistence Item-ID 759069ec-dab9-4193-8d30-61f414e1b6c2
> OperationType MAIO_CommitBatch Status -1061151998 ErrorInfo The published
> message could not be routed because no subscribers were found. Please use the
> Health and Activity Monitoring (HAT) tool to diagnose this situation. .
>
> Exception type: PersistenceItemException
> Source:
> Target Site:
> Help Link:
> 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.
> Please use the Health and Activity Monitoring (HAT) tool to diagnose this
> situation. with status -1061151998.
>
> Exception type: PublishMessageException
> Source:
> Target Site:
> Help Link:
> Additional error information:
>
> Exception occurred when persisting state to the database.
>
> Exception type: PersistenceException
> Source: Microsoft.XLANGs.BizTalk.Engine
> Target Site: Void
> Commit(Microsoft.BizTalk.Agent.Interop.IBTMessageBatchEx[],
> Microsoft.XLANGs.Core.Segment,
> Microsoft.BizTalk.Agent.Interop.IBTOperationStatus ByRef)
> Help Link:
> Additional error information:
>
> A batch item failed persistence Item-ID 759069ec-dab9-4193-8d30-61f414e1b6c2
> OperationType MAIO_CommitBatch Status -1061151998 ErrorInfo The published
> message could not be routed because no subscribers were found. Please use the
> Health and Activity Monitoring (HAT) tool to diagnose this situation. .
>
> Exception type: PersistenceItemException
> Source:
> Target Site:
> Help Link:
> 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.
> Please use the Health and Activity Monitoring (HAT) tool to diagnose this
> situation. with status -1061151998.
>
> Exception type: PublishMessageException
> Source:
> Target Site:
> Help Link:
> Additional error information:
>
>
> Thanks in advance!!!!!
> Cindy
|
|
|
|
|