- This topic has 4 replies, 1 voice, and was last updated 9 years, 2 months ago by
.
-
Posts
-
-
I am using two orchestrations. First orchestration calls the second using direct binding through a two-way send port. Second orchestrion has a two-way receive port to send the result back to the first. Every thing is working as it should but I am getting the following exception.
A response message for two-way receive port “Unknown ” is being suspended as the messaging engine could not correlate the response to an existing request message. This usually happens when the host process has been recycled.
Can any one please help me how to resolve it
Thank you
-
I have never used this pattern, but you could try setting the copying the BTS.EpmRRCorrelationToken property from the request message to the response message in the second orchestration.
Which direct binding option are you using?
Have you consider using separate one way send and receive ports and using your own correlation
-
I haven’t used this pattern either. I did try a similar pattern using two one-way send ports, but I had trouble getting that to work so I used a self-correlating port parameter instead (http://www.codeproject.com/KB/biztalk/bts_async_call.aspx). This was for an async communication scenario, but it sounds like you are using synchronous communications. Have you considered just calling the second orch from the first and passing the results as a parameter?
-
I have the same problem, but i set the BTS.EpmRRCorrelationToken value to a random value, new GUID in my case, in the first orchestration before send to the direct binding port and then in the secod orchestration i copy the value from the inputMessage to the outputMessage, so the value remains the same. With this method BizTalk knows how to correlate the response back to the caller.
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.