Redundant Document Persistence Errors
When Trading Networks’s processing rule is used to initiate the RosettaNet process, some of the internal documents gets persisted multiple times in the Trading Networks database. This can happen because:
Both the
Process Engine and
Trading Networks saves the same document in
Trading Networks database.
Trading Networks saves the document, say
DocA without a
ConversationID and
Process Engine saves the same document
DocA with
ConversationID added to the document.
Same outbound message gets sent multiple times when the
Trading Networks’s processing rule is involved in the initiation of RosettaNet process.
pub.client:http service is used for posting the internal document to wm.tn:receive service.