cancel
Showing results for 
Search instead for 
Did you mean: 

Webservice call timing out in ECC 5.0

Former Member
0 Kudos

Hi

When I make a call to a webservice exposed out of ECC 5.0 from a SOAP client - I see the call being taken up by a work process in SM66 - staying alive for a few seconds and then it disappears from SM66 and at the same time I get a error on the SOAP client

Error reading server response: The underlying connection was closed: The request was canceled.

If I run the same method ( sync implementation ) from within R3 - ( SPROXY and then test interface - by submitting an xml payload ) - the query runs for around 25 seconds and comes back with a result payload.

Have anyone experienced this problem ? What ICM timeout parameter needs to be changed - here to solve this problem ?

Accepted Solutions (0)

Answers (1)

Answers (1)

stefan_hainer
Explorer
0 Kudos

Hi,

perhaps the PROCTIMEOUT expires, the timeout parameters of the ICM are configured individualy for euch icm/server_port_<x>, you will find more details in the documentation:

[http://help.sap.com/saphelp_nw70/helpdata/EN/25/7e153a1a5b4c2de10000000a114084/content.htm]

But befor increasing timeouts at random you should find out the actual cause of this error.

Did the ICM actualy close the connection due a timeout or was it closed from the communication partner?

If you increase the trace level of the ICM (transaction smicm) and reproduce the error, the trace file of the ICM (dev_icm) should show the exact error message.

Regards,

Stefan