on 12-21-2015 5:02 AM
Dear guru,
I am getting the below error in PI message monitoring. In ABAP stack it's processed successfully. It is Proxy to SOAP web service scenario. I am using SOAP receiver adapter.
SOAP: Error occurred: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: Response message contains an errorXIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: java.lang.NullPointerException
I was looking for how to solve it in SCN but I can't get the solution.
Thanks.
Regards,
May
Hi July,
Can you check for mandatory fields (1..1) in your webservice structure (Target of your mapping).Your webservice is expecting one of the mandatory field in target structure at their server, which you are not sending, that's why it's throwing this error.
Thanks,
Ambuj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
The the error is because the response from webservice is blank or having special char and the adapter is unable to parse it.
Plesae test the webservice with external tools like SOAPUI and check if it is providing the response.
regards,
Harish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello May,
Is it a sync scenario?
your getting a error response which cant be handled in response mapping, that's why this error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Harish,
When I try with "Do not use SOAP Envelope", I got the internal server error.
SOAP: Error occurred: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: Response message contains an errorXIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Thanks.
Hi,
the problem may be your request message. did you tried the same message with SoaoUI?
Please refer the inaki's reply on below threat
SOAP: response message contains an error XIAdap... | SCN
1. The endpoint is failing to dealing with your message because:
- You format message is not the format message that is expected. This could be because is expecting a deteminated XSD, determinated SOAP or no-SOAP tags, etc.
- The endpoint is failing for another reason (weird)
2. You could put this in the module tab to deal with the SOAP tags:
Hi,
Shall I use my own wsdl file from my side for testing ?
Because when I was testing with my own wsdl file (not external system wsdl), I am getting error too.
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="PARSING">GENERAL</SAP:Code>
<SAP:Stack>java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:394)
If I am wrong, please correct me.
Thanks.
User | Count |
---|---|
82 | |
10 | |
10 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.