cancel
Showing results for 
Search instead for 
Did you mean: 

Receiver SOAP adapter issue

Merina1
Participant
0 Kudos

Dear Experts,

My scenario is IDOC - PI - SOAP. I am facing the below error in RWB :

The error in RWB is :

23.10.2013 16:48:33.609ErrorMP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: GENERAL-0022: Unexpected exception occured: could not execute query
23.10.2013 16:48:33.609ErrorAdapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: GENERAL-0022: Unexpected exception occured: could not execute query
23.10.2013 16:48:33.609ErrorDelivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: GENERAL-0022: Unexpected exception occured: could not execute query.

The transport Protocol is HTTP, Message Protocol is SOAP 1.1

I have referred the below links but its not helpful :

https://scn.sap.com/thread/518981

http://scn.sap.com/thread/182503

Please provide your expert advice on this error.

Thank you,

Merina

Thank you.

Accepted Solutions (0)

Answers (4)

Answers (4)

aashish_sinha
Active Contributor
0 Kudos

HI Merina,

Are you using Query string by any chance? IF so, please uncheck and test.

Regards

Aashish Sinha

Merina1
Participant
0 Kudos

Hi Aashish,

'Use Query String' is in unchecked only.

The Url is : http://<host:port>/wxi/MessageServlet?CommProtocol=SOAP11&CommPartner=PLAIN&MsgClass=IDOC

Thanks,

Merina

subhro_de
Active Participant
0 Kudos

Hi Merina ,

You should take the outbound payload xmls that are thowing error and the ones that are not and test it directly with the  target URL using SOAP UI or a soap client tool.

You may want to use the wsdl provided by the target application - load it into soap ui and populate with different xmls to look at the details - this appears to be some inconsistent/wrong data  going across to your target application which is causing an exception.

Regards

Subhro

Former Member
0 Kudos

Hi Merina,

There should be some issue with your Outbound Payload and the SOAP Action used in your target URL.

Please check with the third party on the SOAP Action and Target URL.

Thanks and Regards,

Kalyan

Merina1
Participant
0 Kudos

Hi Kalyan,

The error is not seen for every message . The error is noticed only sometimes.

Thanks & Regards,

Merina

markangelo_dihiansan
Active Contributor
0 Kudos

Hello Merina,

Do you have/or is using a mapping for fault messages?

Regards,

Mark

iaki_vila
Active Contributor
0 Kudos

Hi Merina,

Only sometimes the endpoint could be down...

One time i got a similar case and the problem was the asnwer which contained a special characteres ( it came sometimes cyrilic or bulgarian characters), then my question for you, is the error presented always with the same XMLs? if you tried with the same XML throws the exception again?

Regards.

Merina1
Participant
0 Kudos

Hi Inaki,

The payload is not the same always.

Regards,

Merina

iaki_vila
Active Contributor
0 Kudos

Hi Merina,

That error seems that the endpoint is throwing an error page or similar. Try with SOAPui with the same XML that you are using in the PI test and check if the call is successful.

Regards.