invalid http response: null - Error in SOAP sync receiver

[Former Member]

Hi,

We are getting the following error in synchronous SOAP receiver connection.

com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid http response: null

note: This inteface is working fine without error in the subsequent run.

Anyone please help me out in this...

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> - <!-- Inbound Message --> - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"> <SAP:Category>XIAdapterFramework</SAP:Category> <SAP:Code area="MESSAGE">GENERAL</SAP:Code> <SAP:P1 /> <SAP:P2 /> <SAP:P3 /> <SAP:P4 /> <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid http response: null</SAP:AdditionalText> <SAP:Stack /> <SAP:Retry>M</SAP:Retry> </SAP:Error>

[Former Member]

Hi Gayathri,

The SOAP receiver adapter is not getting any response from the Target server. If you are using any WS url at the soap receiver side then that WS is not sending any response message to PI soap receiver. From message you can see that, the response message is 'null', null means nothing.

So check with WS developer they might have modified some thing, from synch to asynch WS call. To cross check what is the response payload contains, you can check the http_response trace file present in the dispatcher folder of J2EE engine.

Best Regards,

RK

[Former Member]

Hi RK,

Thanks for your reply.

The problem here is when we receive this error and if we re-trigger this interface, its working fine. And the WS developer confirmed that they have not changed any settings at that time this interface is erroring out.

[Former Member]

Hi Gayathri,

if it's working in second time (after retriggering) it then you have to check the response payload at first attempt and second attempt. So better, check the response payload from http_respose trace file and note down the info for first and second attempt.

If at first attempt it's not getting response payload then you can also WS developer to check it from their end.

Thanks,

RK

[Former Member]

Hi Rajendra,

The same issue I am also facing in production system.

In my case the all the requests are failing after an IIS7.5  upgrade of the Application in production.

The strange thing is that except SAP rest all the applications are able to submit requests and getting proper response also.

We are using a https communication and private key certificate authentication in SAP PI.

Does it look like a PI issue or IIS upgrade  is causing some issue.

Please suggest.

Thanks,

Ashish