- This topic has 5 replies, 1 voice, and was last updated 9 years, 1 month ago by
.
-
Posts
-
-
Hello BizTalk Gurus,
I have a Receive Location / Port which reads xml files from a file share. (InfoPath forms)
A custom pipeline is applied to all incoming messages replacing an XML value. (Submitted –> Received).
Furthermore, some fields are promoted.
There are also several Send Ports, posting XML files to SharePoint Form libraries based on some promoted fields.
e.g SendPort_Test1: Gets every XML from MessageBox having FormName = Test1 AND Status = Received. (FormName and Status are promoted fields).For some reason some messages are processed twice.In this case, I can see two identical messages in a SharePoint library having different names (the GUID of the BizTalk processed message)
The problem is sporadic and I can not reproduce it.Receive Location’s Settings:
FileMask: *.xml
Retry Count: 25
Retry Interval: 5
Rename files while reading
Polling Interval: 120000
Maximum Retry Interval: 300000
Number of messages in a Batch: 20
Maximum Batch size: 102400Any ideas ?
Thanks,
Dimitris -
Hi,
Did you go with debug from start point (receive pipeline) to end point? What is between ports? (Is there an orchestration, or it’s a CBR?) Can it be – that two send port subscribed on same values and send your message to same destination? Or, subscription is “different”, but some conditions are same? And two messageg go to same destination.
-
Hi,
Since the problem occurs sporadically it was not possible for me to debug the pipeline.
A 3rd party application places files on a file share and the receive port gets every XML by applying my custom receive pipeline. (There is no orchestration related to the implementation). Then every send port which has it’s own filtering conditions , picks up a message and posts it to a Sharepoint form library. At this time a send pipeline is also applied to the message in order to keep the initial file name of the message. (This however is not the problem, cause the problem also occurs without using the send pipeline).
If I had 2 send ports with the same filters picking a message at the same time, I think that I would always have duplicates in one or more Libraries.
I did not understand exactly what you mean by “Or, subscription is “different”, but some conditions are same”. Could you please explain?
Thanks.
-
Hi – about subscriptions
I thought about something like
1. Send port filters:
Message type = x or
Incoming portName = In
2/ SendPort filters:
MessageType = Y or
Incoming portName = In
In both cases your different messages will proceed to both ports (twice). Therefore sometimes when subscription is different – but some of conditions are same for different types of messages.
-
OK. I understood what you mean.
The answer to this is that I am absolutely sure that different ports receive different XMLs.There is no XML that could be used to more than one send port.
and this happens because on every send port the filters are like:
1. PromotedFields.FormName = “XX” AND
2. PromotedFields.StateCode = “Received” AND
3. PromotedFields.Version = “1.0”. -
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.