SOAP Receive Location Routing Failure on following correlation message

Hi, I have an orchestration that has a single Receive Port with two operations.  The first operation receives a message from a SQL adapter and initializes the correlation set.  The second message is supposed to come from a SOAP adapter.  When the second message is received, it is suspended and the log shows “The published message could not be routed because no subscribers were found.”  I checked the suspended messages and the properties used for the correlation set were promoted on the message and the appropriate message type was set.  To trouble shoot the problem, I created a File receive location and copied the contents of the suspended message from the SOAP adapter into a new file and dropped it in that location.  That message went through sucessfully and completed the running service instance.  I compared the message received from the SOAP receive location and the message received from the File receive location and they had the same content and the same promoted properties (other than those specific to the Adapter type and the message instance).  As a workaround, I moved the SOAP receive location (one way) into it’s own Receive Port and I have a File Send Port connected directly to that Receive Port (both using the pass through pipeline) and then a File Receive Location connected to my original Receive Port that picks up the file dropped by my intermediate Send Port.  Configured this way, the message gets routed to the appropriate service instance and the orchestration completes successfully.  Any ideas why I can’t get the same message to process directly from the SOAP receive location?