- This topic has 1 reply, 1 voice, and was last updated 9 years, 7 months ago by
.
-
Posts
-
-
Hello,
We have a custom dissassembler pipeline component for disassembling a flat file.
Actually, before Disassembly,there is another pipeline component that does some custom processing.There is a send port that “passthrutransmits” the disassembled messages onto a output folder. The send port subscribes to the Receive Port.
When we pass a large flat file,with thousands of records in it(each record will be dissassembled into
a xml message), it takes around 12 minutes for the entire pipeline to complete.Now we see that only after that pipeline completes in entirety (i.e. after 12 minutes) does the first files
start appearing in the output folder.I was thinking the custom flatfile dissassembler component operates in a “streaming” mode i.e. it dissassembles
a message and posts it to the MessageBox.So the files should start appearing in the out put folder much much
earlier.
Is my understanding correct? if yes, any ideas what is going wrong?Regards,
anon
-
The receive process is managed within a single transaction – receipt of the message and publishing of all component messages happens in a single transaction.
The standard behaviour is to suspend the entire transaction (all messages) if one of the messages fails.
The Xml and FlatFile Disassemblers have a Recoverable Interchange Processing option that allows all good messages to be published and only the individual failures to be suspended.
Both these mechanisms require all component messages to be successfully published before any can be used.
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.