cancel
Showing results for 
Search instead for 
Did you mean: 

Proxy to SOAP Async Scenario: Error SOAP: call failed: java.io.IOException: invalid http response: null

Former Member
0 Kudos

Hi,

We are developing one Proxy to SOAP Async scenario.

SOAP WSDL has both request & response structures, but where we are using only one structure to send out data.

Whenever we send data from Proxy, vendor(no firewall) is receiving information and able to process it successfully.

Here the problem is in PI, for few messages in RWB it is showing success message.

Information MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean

Information SOAP: request message entering the adapter with user J2EE_GUEST

Information SOAP: completed the processing

Information SOAP: sending a delivery ack...

Information MP: leaving

Information The message was successfully delivered to the application using connection SOAP_http://sap.com/xi/XI/System.

And for some messages(mostly with data of higher volume >900 KB), turning out to error in RWB. But Partner side, they are getting data and able to process it.

Information MP: processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean

Information SOAP: request message entering the adapter with user J2EE_GUEST

Error SOAP: call failed: java.io.IOException: invalid http response: null

Information SOAP: sending a delivery error ack...

Information SOAP: sent a delivery ack

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

Error Adapter Framework caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid http response: null

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: java.io.IOException: invalid http response: null.

If anyone faced such issue earlier or have any idea of such issues, please throw some light.

Thank You.

Veneela

Accepted Solutions (0)

Answers (3)

Answers (3)

markangelo_dihiansan
Active Contributor
0 Kudos

Hello,

Is your processing taking longer than 5minutes? If yes, add this to the module configuration of the XISOAPAdapterBean.

ModuleKey                                    ParameterName               Parameter Value

KeyForSOAPAdapterBean              XMBWS.Timeout              600000

600000 is 10 minutes. My source is http://scn.sap.com/docs/DOC-16238

Edit: It looks like the note provided by Inaki uses XI.Timeout but is only available for SP13 and above.

Hope this helps,

Mark

Former Member
0 Kudos

Hi,

    Thanks for responding.

I'm working on 7.1 SP07 version. Since this scenario is Async, XMBWS.Timeout parameter is not working.

I have tried that option with parameter value 600000.

Regards.

Veneela

iaki_vila
Active Contributor
0 Kudos

Hi Veneela,

Try to increase the SOAP receiver timeout XMBWS.Timeout in the module adapter table, 600000 represents the timeout value of 10 minutes. Check  856597  - FAQ: XI 3.0 / PI 7.0/7.1/7.3 SOAP Adapter the question Q: Can I configure the timeout value of my receiver adapter?

Regards.

former_member192343
Active Contributor
0 Kudos

Hi Veneela,

did you try this note 1456688 ? Maybe it will help