on 05-06-2015 11:09 AM
Hello All,
I have a synchronous PROXY to SOAP scenario. The interface was working fine , but it is strange that it is started throwing exception at proxy end (response message) .
The messages pass through PI successfully and even in ABAP moni the messages are successful. However in the proxy it throws above exception.
The interface was working perfectly fine earlier. And there has been no change in the dev and all of a sudden we are getting the above exception.
Any suggestions what could have gone wrong?
PS: There is no change in the response message being sent from target.
Thanks in Advance,
Anumeha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Anumeha,
From the screenshot it looks to be data mis-match issue. Can you check the XML Path & its value to which this error points to.
Is this failing for all the messages or few of them? Cross Check in moni the payload & data that is getting populated in Proxy.
Regards,
Azhar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Then seems to be issue in the Data that is being sent back from 3rd Party.
1.Can you test the Receiver side WSDL, using SOAP UI tool and check what data you are getting back. It should match with your expected Proxy Response structure.
2. Alternatively you can also pick the Response Payload from Moni and try to test in MM - ESR and check if its getting executed successfully.
Regards,
Azhar
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.