AIA Async delayed response pattern :RequestorABCS remains in suspended mode

Question

Hi All,
I am trying to implement the Async delayed response pattern for one of my integration flows. After there is a fault on providerABCS it creates the responseEBM along with fault message in it and invokes the ResponseEBS. The ResponseEBS shows as completed and has invoked the desired operation on RequestorABCS. However the RequestorABCS shows as Pending status on the receive activity.
I have created correlation ids and sets on both Invoke and Receive in requestorABCS as below:
<invoke name="Invoke_EBS"
inputVariable="Invoke_EBS_CreateAccountingEntryList_InputVariable"
partnerLink="JournalEntryEBS" portType="ns1:AccountingEntryEBS"
operation="CreateAccountingEntryList">
<correlations>
<correlation initiate="yes" set="CorrelationSet_1" pattern="out"/>
</correlations>
</invoke>
<receive name="Receive_Response" createInstance="no"
variable="Receive_Response_updateResponse_InputVariable"
partnerLink="createjournalentryxxxreqabcsimpl_client"
portType="client:CreateJournalEntryXXXReqABCSImpl"
operation="updateResponse">
<correlations>
<correlation initiate="no" set="CorrelationSet_1"/>
</correlations>
</receive>
The property aliases are as below:
<bpws:propertyAlias propertyName="pns1:Identifier" xmlns:ns1="http://xmlns.oracle.com/EnterpriseServices/Core/AccountingEntry/V1"
messageType="ns1:CreateAccountingEntryListReqMsg" part="CreateAccountingEntryListEBM"
query="/ns2:CreateAccountingEntryListEBM/ns3:EBMHeader/ns3:EBMID" xmlns:ns3="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2"/>
<bpws:propertyAlias propertyName="pns1:Identifier" messageType="client:CreateJournalEntryResponseMessage"
part="CreateJournalEntryResponseMessagePart" query="/ns2:CreateAccountingEntryListResponseEBM/ns3:EBMHeader/ns3:RequestEBMID"
xmlns:ns3="http://xmlns.oracle.com/EnterpriseObjects/Core/Common/V2"/>
And the operation I am trying to invoke from ResponseEBS is updateResponse:
<wsdl:portType name="CreateJournalEntryXXXReqABCSImpl">
<wsdl:operation name="process">
<wsdl:input message="client:CreateJournalEntryXXXReqABCSImplRequestMessage"/>
</wsdl:operation>
<wsdl:operation name="updateResponse">
<wsdl:input message="client:CreateJournalEntryResponseMessage"/>
</wsdl:operation>
In providerABCS I am mapping the EBMID from requestEBM to RequestEBMID on responseEBM. Any suggestions on what could be going wrong here ?
Thanks
Subhankar

Answer 1

Hi Rahul
I have added the namespace ns2 defined in both property alias and retested. Its still the same issue. Below is the entire EBM header being sent to RequestorABCS
<part name="CreateJournalEntryResponseMessagePart">
<ns0:CreateAccountingEntryListResponseEBM>
<corecom:EBMHeader>
<corecom:EBMID>35343732313139303739373930373630</corecom:EBMID>
<corecom:EBMName>{http://xmlns.oracle.com/EnterpriseServices/Core/AccountingEntry/V1}CreateAccountingEntryListEBM</corecom:EBMName>
<corecom:EBOName>{http://xmlns.oracle.com/EnterpriseServices/Core/AccountingEntry/V1}CreateAccountingEntryEBO</corecom:EBOName>
<corecom:CreationDateTime>2010-09-29T10:19:05-05:00</corecom:CreationDateTime>
<corecom:RequestEBMID>32303139353537383031333433333039</corecom:RequestEBMID>
<corecom:VerbCode>Create</corecom:VerbCode>
<corecom:MessageProcessingInstruction>
<corecom:EnvironmentCode>PRODUCTION</corecom:EnvironmentCode>
</corecom:MessageProcessingInstruction>
<corecom:Sender>
<corecom:WSAddress>
<wsa:ReplyTo>
<wsa:ServiceName>CreateJournalEntryXXXReqABCSImpl</wsa:ServiceName>
</wsa:ReplyTo>
</corecom:WSAddress>
</corecom:Sender>
<corecom:BusinessScope>
<corecom:ID>YYY-XXX-Create-Accounting-Entry</corecom:ID>
<corecom:InstanceID>CreateAccountingEntry/34353438393635303036303932373734</corecom:InstanceID>
<corecom:BusinessScopeTypeCode>BusinessProcess</corecom:BusinessScopeTypeCode>
<corecom:EnterpriseServiceName>{http://xmlns.oracle.com/EnterpriseServices/Core/AccountingEntry/V1}AccountingEntryEBSV1</corecom:EnterpriseServiceName>
<corecom:EnterpriseServiceOperationName>CreateAccountingEntryList</corecom:EnterpriseServiceOperationName>
</corecom:BusinessScope>
<corecom:FaultNotification>
<corecom:ReportingDateTime>2010-09-29T10:20:33-05:00</corecom:ReportingDateTime>
<corecom:CorrectiveAction/>
<corecom:FaultMessage>
<corecom:Code>{http://schemas.oracle.com/bpel/extension}bindingFault</corecom:Code>
<corecom:Text>oracle.fabric.common.FabricInvocationException</corecom:Text>
<corecom:Severity/>
<corecom:Stack>null</corecom:Stack>
</corecom:FaultMessage>
<corecom:FaultingService>
<corecom:ID>CreateJournalEntryYYYProvABCSImpl</corecom:ID>
<corecom:ImplementationCode>BPEL</corecom:ImplementationCode>
<corecom:InstanceID>1870131</corecom:InstanceID>
<corecom:ExecutionContextID/>
</corecom:FaultingService>
</corecom:FaultNotification>
</corecom:EBMHeader>
</ns0:CreateAccountingEntryListResponseEBM>
Regards
Subhankar