SOAP Receiver Error - Recoverable Exception

Can someone please explain why I am getting this:
Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error Application/UNKNOWN/APPLICATION_ERROR - application fault.

Yeah, since it's an application fault.
If you have sync2sync scenario, you can map this fault message to an exception in outbound interface.
If you have bpm calling the web service, you can catch the fault message and execute and exception branch in bpm.
Regards,
Henrique.

Similar Messages

SOAP Receiver error - HTTP 500 Internal Server Error

Hi,
We have a FILE to SOAP Asynchronous scenario to send data from our PI to customer PI.
We are sending PGP encrypted file as the payload. So, foll settings have been maintained:
Do not use SOAP envelope in Sender and Receiver SOAP
nosoap=true in the URL.
Message transform bean in the SOAP channels.
File is successfully sent and received through SOAP protocol.
But, both the SOAP Receiver and Sender channels are in error:
SOAP Receiver error:
SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error.
As, this is a asynch scenario, we are not expecting the response.
SOAP sender at customer PI is in error. Error text is not mentioned. It just displays: error occured.
At both the ends, we do not have Repository objects as there is no mapping.
Kindly help...
Thanks,
Pratibha.

Hi All,
For the same scenario, we need to Sign the data using the WebServices Security.
(We are sending PGP encrypted data as SOAP payload using MTB, i have ticked "Do not use SOAP envelope")
I have selected WebServicesSecurity as the security profile in the SOAP Receiver and selected "Sign" in the Receiver agreement, have provided our private cert.
Tried sending a message. Communication channel audit Log shows the message:
Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
Success SOAP: request message entering the adapter with user J2EE_GUEST
Success SOAP: Web Services Security processing...
Success SOAP: Web Services Security processing skiped. Empty body...
Success SOAP: completed the processing
Please suggest how I can apply the WSS..
Thanks,
Pratibha.

SOAP Receiver Error.

Hi Experts,
The scenario is esell system to SOAP receiver. we shared the wsdl for the partners.
during testing i am facing the below error in the SOAP receiver comm channel.
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: http://sap.com/xi/WebService/soap1.1.
Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER_SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: http://sap.com/xi/WebService/soap1.1.
NOte: The WSDL which shared with parter has soap action. how should i fix this error.
When we ask our partners they are telling that they have loaded the wsdl which we provide.
Could anyone throw some light on how to fix the issue.
Thanks,
--Sai.

Hi Sai,
I Agree with Bhaskar please check the below blogs for reference...
RFC -> XI -> WebService - A Complete Walkthrough (Part 1)
RFC -> XI -> WebService - A Complete Walkthrough (Part 2)
Thanks and Regards,
Naveen

SOAP Receiver - Error in response

Hi Experts,
Please help me with follow.
I have a Interface RFC -> SOAP and in SXMB_MONITOR is OK. But receiver system the data don't OK.
In the Communication Channel i see the error message:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 503 Service Unavailable
and in Message Monitoring (Message Display), the error message:
2009-03-05 09:01:15 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 503 Service Unavailable
2009-03-05 09:01:15 Error Exception caught by adapter framework: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 503 Service Unavailable
2009-03-05 09:01:15 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 503 Service Unavailable.
But the Webservice is ok and the parameters of the communication channel (URL, Action and other) too.
Thanks in advance.

Hi Pedro,
HTTP Error 503 basically indicates service unavailability.
Check out the following thread : Http 500 internal server error while calling webservice
http://www.checkupdown.com/status/E503.html
Thanks,
Pooja Pandey

SOAP Receiver Error: HTTP Error response for SOAP Request

Hi gurus,
I'm facing a weird error in File --> PI 7.31 java only --> soap receiver proxy.
The other interfaces runs well. just one get the the following error:
Exception caught by adapter framework: java.io.IOException: Error receiving or parsing request message: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.
I check the payload and test in the inbound proxy. on error.
Any hints?
Thanks a lot!
regards
Christine

Hello Christine,
I faced the same issue,
You can use the beans below to overcome the error.
And charset should be utf-8

SOAP receiver: error HTTP 302 (Moved Temporarily)

Dear all,
I configured scenario where SOAP web service is consumed from SAP ABAP system via PI. The problem is in communication with the web service: the error observed in communication channels monitor for the configured SOAP receiver channel is:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: invalid content type for SOAP: TEXT/HTML; HTTP 302 Moved Temporarily: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 302 Moved Temporarily
The consumed web service is based on the function module developed in SAP NetWeaver 7.00 system. Endpoint for the service was then created via SOAMANAGER, generated binding's address was used as a target URL in the SOAP receiver channel.
If the service is consumed not via PI, but tested directly from external SOAP client (I used soapUI) with the same WSDL and endpoint, the response is fine and error-free.
Please advise possible root cause of the issue.
My regards,
Vadim

Hi,
I am working on a similar scenario where I my consuming an external web service using https protocol from PI.
I have configured a soap receiver channel to call the target url of this web service as https://portal.xyz.org.uk/webservice_alt.
I am getting an error HTTP 302 suggesting that PI is not able to follow the re-direction to the target URL as the service resides not on that URL but on https://portal1.xyz.org.uk/webservice_alt or https://portal2.xyz.org.uk/webservice_alt.
This is their server fail over handling mechanism which is very common. But PI 7.0 is not able to handle this.
So if I change the target URL on the SOAP receiver channel to https://portal1.xyz.org.uk/web service or https://portal2.xyz.org.uk/webservice_alt , PI works fine without errors . But this is not the right approach because, every time the web service provider takes one of these systems down for upgrade/patching etc, they inform us and then I manually go and change the target URL to the available server on my production PI system config.
My problem is I want to resolve this redirection error in PI. I have tried raising a call with SAP itself and they pointed out to use Axis adapter which is still not working.
So I am here asking for help. any suggestions please from the experts?
Thanks
Jhansi.

SOAP Receiver error in PI 7.1

Hi Experts,
Please help me with follow.
I have a Interface Proxy -> SOAP and in SXMB_MONITOR is OK. But receiver system the data don't OK.
In the Communication Channel i see the error message:
2009-04-29 11:20:24 Error SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Internal Error
2009-04-29 11:20:24 Information SOAP: sending a delivery error ack ...
2009-04-29 11:20:24 Information SOAP: sent a delivery error ack
2009-04-29 11:20:24 Error Adapter Framework caught exception: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Internal Error
2009-04-29 11:20:24 Error Delivering 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: Internal Error.
2009-04-29 11:20:24 Information The message status was set to WAIT.
But the Webservice is ok and the parameters of the communication channel (URL, Action and other) too.
Thanks in advance.

check this one:
Async Scenario converted to Sync by PI

SOAP Receiver- Error While Sending Message: 500 Internal Server Error

Hello,
Our scenario: IDoc to SOAP
I have added a third party system in the SLD and have used the same in my ID configuration.
An idoc will be triggered from R/3, which will received in PI, PI will transform the IDoc into SOAP message for the third party system.
I have tested the scenario in ID from Interface Determination and its successful.
But when i try to try to test it from RWB, using Test Message in Adapter Engine, I get an error,
"Error while sending message:500 Internal server error"
If we test it using a testing software like SOAP UI, it works fine but from PI we get the error mentioned above.
Regards,
Abhishek

Hello,
Since the IDOC adapter resides on the ABAP stack, you can use this URL instead (it will be sent to the integration engine as Venkata suggested)
http://host:port/sap/xi/engine?type=entry
Also check your firewall settings from PI to the third-party system.
Hope this helps,
Mark
Edited by: Mark Dihiansan on Feb 7, 2012 11:48 AM

SOAP (Receiver): error occured: Connection refused:

Hi experts,
I have a RFC -> XI -> SOAP scenario and while testing the same it gets cancelled with the following errors:
SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect
MP: exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect
Exception caught by adapter framework: Connection refused: connect
Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Connection refused: connect: java.net.ConnectException: Connection refused: connect.
Please help me out.
Regards,
Daniela

Hi,
1. Either the SOAP Url in the SOAP adapter is wrong,
2. Or there is a proxy server between XI and the Webserivce and so provide the proxy server details in the SOAP adapter ( with Authentication ) if needed and give it a shot.
Regards
Bhavesh

Error while signing in SOAP receiver channel

Hi,
I have a Source PI which is sending a XML message to a target PI through SOAP adapter. Its a secure commnication. I am using message level encryption and signing on the source receiver agreement and message level decryption and validation on target sender agreement. The message is failing in the SOAP receiver cahnnel on source PI with the below error message. Also, I am using a certificate which is signed by Verisign and its valid for two years. I have checked the validity, it has not expired yet.
It works fine if the certificate is signed by SAP(that is, test certificate which is valid for 8 weeks).
Error Message
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIServer/UNKNOWN/ADAPTER.JAVA_EXCEPTION - com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: verify( Message, byte[], CPALookupObject ). Message: SecurityException in method: verify( Message, byte[], CPALookupObject ). WSSEThread-Exception: SecurityException in method: run(). Message: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.).. To-String: com.sap.security.core.policy.exceptions.VerifyException: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.).; To-String: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: run(). Message: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.).. To-String: com.sap.security.core.policy.exceptions.VerifyException: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.).. To-String: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: verify( Message, byte[], CPALookupObject ). WSSEThread-Exception: SecurityException in method: run(). Message: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.).. To-String: com.sap.security.core.policy.exceptions.VerifyException: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.).; To-String: com.sap.aii.security.lib.exception.SecurityException: SecurityException in method: run(). Message: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.).. To-String: com.sap.security.core.policy.exceptions.VerifyException: [_policy0230] The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.). at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:996) at sun.reflect.GeneratedMethodAccessor546_10002.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:43) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:38) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16) at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177) at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133) at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164) at $Proxy2684_10002.process(Unknown Source) at com.sap.aii.af.app.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:275) at

Hi,
as per the error message is:
"... The part /soap:Envelope/soap:Body was required to be signed by the policy with the transformations [], but the signature was not accepted. (Info: number of valid signatures: 1, number of accepted signer certificates: 0.) ..."
I guess the cert. setup either on your side or the other system's side is not fully correct. Check whether all cert., priv keys and public keys are exchanged propperly and setup as trusted certs.
Regards,
Kai
Edited by: Kai Lerch-Baier on Jul 9, 2009 1:24 PM

Error in SOAP receiver channel in Synchronous Proxy to SOAP scenario

Hi all,
We are experiencing an issue with a synchronous Proxy to SOAP scenario. Getting below error message in the SOAP receiver communication channel for the response message.
SOAP: Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error encountered while executing mapping: com.sap.aii.af.service.mapping.MappingException: com.sap.aii.utilxi.misc.api.ResourceException: Could not determine mapping steps for message 1364b76e-ecbf-11e4-85f4-000023acfde6.
We are running PI 7.4.
Any help is appreciated.
Thanks,
Pushpa

Hi,
Seems the Receiver Webservice is not reachable. Did you try to test it using SOAP UI tool.
1. Test a fresh message from local SOAP UI tool.
2. Pick 3rd party WSDL file and Import in SOAP UI tool.
3. Put some dummy data for mandatory fields
4. Trigger it msg and ckh if you get successful / response msg.
5. Check if firewall is open and that URL is not blocked.
Hope it helps
Regards,
Azhar

SOAP Receiver Adapter Error in XI RWB - java.lang.NULLPointerException

Hi,
We have a asynchronous scenario in SAP-XI, where we are sending the PO data from SRM to third party (Hubspan / TNT). Proxy is being used at Sender side and SOAP Adapter is used for Receiver Communication Channel.
u2022SRM is sending around 1000 messages through background job and around 995 or 996 messages are being processed successfully and showing the proper XML payload as well in RWB. But 4-5 messages are getting failed in XI RWB for u2018java.lang.NullPointerExceptionu2019. For these failed messages we are not able to see the XML payload as well in XI RWB while these messages are showing successful status in MONI in SRM and XI and we are able to see the payload as well in MONI. The webservice is restarting and trying to send the payload three times in RWB, but it is getting the same Nullexception error.
04.11.2011 16:45:49.715 Success Delivering to channel: CC_B2B_HUBSPAN_RCV
04.11.2011 16:45:49.715 Success MP: Entering module processor
04.11.2011 16:45:49.715 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
04.11.2011 16:45:49.716 Success SOAP: request message entering the adapter with user J2EE_GUEST
04.11.2011 16:45:49.716 Success SOAP: Target url: https://connect.hubspan.net/mh/server/tp=NMHG/ssid=DAA6F0E9AC1000BD03A41B363BBFD676
04.11.2011 16:45:49.999 Error SOAP: call failed: java.lang.NullPointerException
04.11.2011 16:45:49.999 Success SOAP: sending a delivery error ack ...
04.11.2011 16:45:49.999 Success SOAP: sent a delivery error ack
04.11.2011 16:45:49.999 Error SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.NullPointerException
04.11.2011 16:45:49.999 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.NullPointerException
04.11.2011 16:45:50.000 Error Exception caught by adapter framework: null
04.11.2011 16:45:50.022 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.NullPointerException.
04.11.2011 16:45:50.037 Success The message status set to WAIT.
u2022If we are resending the failed message from XI RWB, it is getting failed again with the same error. On the other hand if we are initiating the message again from SRM to Hubspan for the same PO, it is getting processed successfully in RWB but still not showing XML payload in RWB.
u2022If we are getting the payload from XI MONI for the failed message and doing a test with component monitoring in RWB, it is working fine.
Please help me to solve this issue.
Thanks
Sumit

Hi Sumit,
From my experience, when you transfer SAP POs through PI to external webservice, there should be some validation happens at the webservice layer of the target system before the web service passes the original information to their application layer. The validation can be anything like checking the Vendor address, Checking the correctness of the order ...etc etc . So i would suggest to ask your external web service folks to check if they have any validation in place before they pass the data to their application layer.
As you said only some POs/XMLs are failing, i strongly feel that this could be the issue.
Please note if you receive response code other than 200 from webservice, SOAP adapter treats that as error and send the same message back to AE.
Normally webservices won't send 200 code for any validation error
PS: you can still try to use XMLSpy to post the failed message to the web service to know the exact cause.

Soap Receiver adapter - 401 error

I am getting following error with soap receiver,
com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 401 Unauthorized
I am able to consume the webservice with SOAP UI without any difficulty. I have tried with both the endpoint URL and WSDL url without success. I have tried with/without 'Do not use SOAP envelope'. I am not sure what is wrong. When the message is sent via PI, he is not able to look at the payload (while performing the trace) , while he is able to view the actual soap message with SOAP UI.
When i type the ENDPOINT url in my http address, i get a 'page not found' error.
Any ideas as to what i could be missing?

One more interesting behaviour when I was sending from SOAP UI, The request was posted twice, meaning there were two POST actions in my TCPGATEWAY listening port, while there was only one request via PI.
Wnen my partner put a trace, the SOAP envelop was missing in their TRACE for PI file while the SOAP envelop was available for SOAP ui message (in the second request). Could it have something to do with a fact that we are doing HTTP 1.1with soap uI While PI is HTTP 1.0 (HTTP 1.1 being a persistent connection resulting in second request)
Trace on the partner side,
PI Message
POST /Services/Calculator/Version1/Calculator.asmx HTTP/1.0
accept: * / *
host: www.html2xml.nl
user-agent: SAP-Messaging-com.sap.aii.af.sdk.xi/1.0505
callingtype: SJM
content-id: <soap-4EB90CC8537E011DE1008000CDEB6913>
content-type: text/xml; charset=utf-8
content-length: 888
SOAPAction: "http://tempuri.org/Add"
HTTP/1.0 401
WWW-Authenticate: Basic realm="CASM"
Content-Type: text/html;charset=utf-8
Content-Length: 40
Date: Thu, 10 Nov 2011 11:50:13 GMT
Connection: close
SOAP UI log
POST /Services/Calculator/Version1/Calculator.asmx HTTP/1.1
accept-encoding: gzip,deflate
content-type: text/xml;charset=UTF-8
soapaction: "Create"
user-agent: Jakarta Commons-HttpClient/3.1
host: www.html2xml.nl
content-length: 2496
HTTP/1.1 401
WWW-Authenticate: Basic realm="CASM"
Content-Type: text/html;charset=utf-8
Content-Length: 40
Date: Thu, 10 Nov 2011 12:04:40 GMT
POST /Services/Calculator/Version1/Calculator.asmx HTTP/1.1
accept-encoding: gzip,deflate
content-type: text/xml;charset=UTF-8
soapaction: "Create"
user-agent: Jakarta Commons-HttpClient/3.1
content-length: 2496
authorization: Basic U1lTX1dFQl9TQVBQSTo=
host: www.html2xml.nl
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
</soapenv:Envelope>
HTTP/1.1 200
Set-Cookie: JSESSIONID=A48C8808315935EFD7AFBA8B4B96FC62; Path=/xx
Keep-Alive: timeout=1200000, max=1000
Connection: Keep-Alive
Content-Encoding: gzip
Content-Type: text/xml;charset=utf-8
Content-Length: 2882

SOAP Receiver adapter error. SOAP CALL Failed

Hi ,
I am implementing scenario R/3->RFC adapter->XI->SOAP REceiver adapter->Web Service (Synchronous). I am getting the error.
SOAP: call failed
SOAP: error occured: java.net.ConnectException: Connection timed out
Message log is as below.
Any clue ?
Thanks & Regards,
Mathew
2005-10-31 18:59:58
Success
output
1130810398454
The message was successfully received by the messaging system. Profile: XI URL: http://host:Port/MessagingSystem/receive/AFW/XI
2005-10-31 18:59:58
Success
output
1130810398458
Using connection AFW. Trying to put the message into the request queue.
2005-10-31 18:59:58
Success
output
1130810398458
Message successfully put into the queue.
2005-10-31 18:59:58
Success
output
1130810398459
The message was successfully retrieved from the request queue.
2005-10-31 18:59:58
Success
output
1130810398459
The message status set to DLNG.
2005-10-31 18:59:58
Success
output
1130810398460
Delivering to channel: CC_CALCULATOR
2005-10-31 18:59:58
Success
output
1130810398564
SOAP: request message entering the adapter
2005-10-31 19:03:07
Success
output
1130810587497
SOAP: call failed
2005-10-31 19:03:07
Error
output
1130810587497
SOAP: error occured: java.net.ConnectException: Connection timed out
2005-10-31 19:03:07
Error
output
1130810587498
Exception caught by adapter framework: Connection timed out

Hi Mathew,
Check if the webservice is availble??? Based on the error below, it looks like the message is timing out at the Adapter Engine level waiting for the connection to make the webservice call...
Prasad

No SOAP Envelope error in SOAP Receiver Adapter

Hello Friends,
Informaiton:-
I have configured one Synchronous scenarion for SAP R/3 to PI 7.1 to Java based web applicaiton.
On the Receiver/Outbound side, i have configured the SOAP Receiver Adapter with the Target URL and SOAP Action.
Outbound and Inbound service interfaces have Request/Response and Fault messages.
Issue:-
While sending the Message, Below error is noticed in ABAP stack SXMB_MONI during the Call Adapter Stage and also in RWB (Channel Monitoring) .
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: No SOAP Envelope but 1 {}RESPONSES; HTTP 200 OK
I also found that Request message is not reaching to the Java Web server.
I am taking the Same message Payload (found at Call Adapter Stage) and ussing it in XML Altova SPY Web client tool. There it is running scuccessfully and getting the Response message.
please suggest.
Thanks & Regards
Jagesh

Hi,
Yesterday i consumed the same WSDL file in Altova XML SPY and there it is working, getting the Response.
Now comparing the SOAP Request message reaching to the Third party Web server (which fall within the same Lane network)
from SAP PI and Altova XML SPY tool. I used TCP Gateway for the below scenarios.
(1)First i sent the SOAP message from PI and observed the RESPONSE message without the SOAP Envelope in TCP Gatway Trace and hence i am getting the No SOAP Envelope Error in PI.
(2)I consumed the same WSDLfile in Altova XML SPY and sent the SOAP message, here i got the Proper SOAP Response message and hence success in this case. (Used the same Data Payload as used in point 1)
(3)Now to identify the issue in the SOAP Request message being sent from PI, i used the same SOAP message sent in step 1 here, that means copy the entire SOAP ENvelope from the TCP gateway Trace and pasted it in Alota Spy and sent, there it is found running (got the response message from Third Party server).
One difference i found in HTTP Protocol statements in SOAP Request message in Point no 1 and Point no 2 above.
HTTP Protocols in Point 1 (Through PI).
POST HTTP/1.0
Accept: /
Host: 172.24.138.142:4544
User-Agent: SAP-Messaging-com.sap.aii.af.sdk.xi/1.0505
CallingType: SA
content-id: <soap-00306EEAC2051ED1839136CEE8564900 sap.com>
Content-Type: text/xml; charset=utf-8
Content-Length: 1195
SOAPACTION: "Action1"
HTTP Protocols in Point 2 (Through Altova).
POST / HTTP/1.1
Content-Type: text/xml
User-Agent: XML Spy
SOAPAction: "Action1"
Host: 172.24.138.142:4544
Content-Length: 1195
Connection: Keep-Alive
Cache-Control: no-cache
Thanks to Mr. Stefan Grube for writting such a nice blog.
Troubleshooting SOAP, HTTP and Mail Adapter Scenarios with TCPGateway
Experts, please suggest me further.
Thansk & Regards
Jagesh

SOAP Receiver Error - Recoverable Exception

Similar Messages

Maybe you are looking for