SAP Knowledge Base Article - Preview

1987486 - How to adjust timeout settings for webservice calls going out from SAP AS Java system

Symptom

There is a webservice which needs more time to be executed and the client times out with error prematurely.

This KBA summarizes how to set up timeout for webservice calls on SAP Java Webservices framework.

Typical timeout error message:

Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Connection IO Exception. Check nested exception for details. (Read timed out).
Caused by: java.net.SocketTimeoutException: Read timed out

-----
Connection IO Exception. Check nested exception for details. (Read timed out).

[EXCEPTION]

com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Connection IO Exception. Check nes ted exception for details. (Read timed out).

at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.outputSOAPMessage(SOAPTransportBinding.java:420)

at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1365)

at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:991)

at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:945)

at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)

at com.sap.engine.services.webservices.espbase.wsdas.impl.WSDASImpl.invokeOperation(WSDASImpl.java:119)

at com.sap.engine.services.sca.plugins.ws.WebServiceImplementationInstance.accept(WebServiceImplementationInstance.java:152)

at com.sap.engine.services.sca.das.SCADASImpl.invokeReference (SCADASImpl.java:190)

-----

Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at iaik.security.ssl.Utils.a(Unknown Source)
at iaik.security.ssl.o.b(Unknown Source)
at iaik.security.ssl.o.c(Unknown Source)
at iaik.security.ssl.k.b(Unknown Source)
at iaik.security.ssl.k.a(Unknown Source)
at iaik.security.ssl.k.read(Unknown Source)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:903)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:383)
at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:292)
at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:421)


Read more...

Environment

SAP NetWeaver AS Java as of release 7.10

Product

SAP NetWeaver 7.1 ; SAP NetWeaver 7.2 ; SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5

Keywords

SOA NWA timeout webservice configuration, consumer, java, single configured, "Max wait-time", transport settings, Application and Scenario Communication, Application Communication, mass configured , KBA , BC-ESI-WS-JAV-CFG , Configuration , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.