Persistence Exception + Routing Failure
Often I'll get the following error:
HAT doesn't seem to show anything in error and its all a bit misleading.
This is usually because I have a direct messagebox send somewhere after where HAT shows the orchestration position. I'm getting the persistence error because the thing that's supposed to be subscribing to the (direct sent) message is an independent send port which hasn't had its filter set or set correctly (remember you are often setting BTS.MessageType to the schema's target namespace + "#" + the root node name). You have to set a filter on an independent send port - it won't just send everything!
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 72407d67-ec02-4c88-a404-b2af5df17b15 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.
HAT doesn't seem to show anything in error and its all a bit misleading.
This is usually because I have a direct messagebox send somewhere after where HAT shows the orchestration position. I'm getting the persistence error because the thing that's supposed to be subscribing to the (direct sent) message is an independent send port which hasn't had its filter set or set correctly (remember you are often setting BTS.MessageType to the schema's target namespace + "#" + the root node name). You have to set a filter on an independent send port - it won't just send everything!
posted by Ben Cops at
2:24 pm
0 Comments:
Post a Comment
<< Home