View Single Post
  #1 (permalink)  
Old September 19th, 2006, 09:50 PM
cmiller66 cmiller66 is offline
Registered User
 
Join Date: Aug 2006
Location: , , .
Posts: 4
Thanks: 0
Thanked 0 Times in 0 Posts
Default Multiple receive ports in an orchestration

I am having an issue with an orchestration that I am creating that has the following parameters.

I receive a message (XML) on a Request/Response port. The message is then sent to a send port that passes the message to the MSMQT. The MSMQT passes the message to an application. After the app does its processing, it passes a Response XML file back to a different MSMQ queue (part of the architecture unfortunately). A receive port listening in on the second MSMQT takes the message, passes the message to the Response part of the port operation.

I set the first receive message initializes the BTS.MessageID as the correlation set property. The remaining messages use that correlation set. The issue is that when I build the solution, I get the following error:

"in a sequential convoy the ports must be identical."

I researched this issue and found that this issue occurs when you do not share a receive port.

I was wondering if anyone has encountered this problem and found a way around it. I have to stay with the 2 receive port system. Would separating the orchestration into two work? I should be able to use the BTS.MEssageID property in that second orchestration.

Any help would be greatly appreciated on this issue.

Reply With Quote