Connection to partner timed out after 0s

[Former Member]

Hi, we're having some problems with our Web Services published by Enterprise Services, this is the message:

500 Connection timed out

---

Error:	-5
Version:	7000
Component:	ICM
Date/Time:	Tue Jul 10 10:22:27 2012
Module:	icxxthr.c
Line:	2698
Server:	webdispatcher_WD2_01
Error Tag:	{-}
Detail:	Connection to partner timed out after 0s

© 2001-2005, SAP AG

Randomly we're having this message with one of our WS, we have 5, and the others never had this message as response, the curious thing here is that i have searched in google and all the related messages are like "Connection to partner timed out after 60s", "Connection to partner timed out after 90s", but never 0s.

We found this note 824554, that says we have to add this parameters:

• icm/conn_timeout
• icm/keep_alive_timeout
• icm/server_port_< n >

Our Basis team added this parameters with 600s but we're still receiving randomly the message with 0s, don't know what else to do.

Thanks for any help.

[anja_engelhardt2]

moved from Portal forum to SAP Netweaver Application Server forum

[hofmann]

Does the connection really time out after 0s or does it actually take longer and only the message shown is wrong?

You mention that from your 5 WS this happens only to 1. Is this a long running WS that simply takes longer to respond? Besides this, can it be that maybe simply the connection gets terminated by the WS server, like: the data send to the WS is wrong and the server terminates the connection?

[Former Member]

Yes, the connection time out instantly, looks like is not waiting for our 600s, maybe we need to check company bandwidth but we're trying to check if the problem is in Sap server.

That WS can take a little longer, at top 35s, because it makes 3 SAP documents, but the connection returns the time out response while sap keeps creating the docs, SAP's not waiting to complete the process.

Data is ok because First call comes, starts to create the documents, somehow returns a response with the timeout (SAP still creating docs) and we have an automatic procedure that if an error returns we try to make documents again, Second call comes and create same documents duplicated.

What i dont understand is if returns a SAP exception message of TimeOut, why SAP keeps creating the docs like nothing happened?

[Former Member]

Hi Gabriel,

You say:

What i dont understand is if returns a SAP exception message of TimeOut, why SAP keeps creating the docs like nothing happened?

Can you elaborate on your architecture? Is there any reverse proxy involved in the communication, is it only SAP Web Dispatcher? Can you try to access the backend directly by bypassing the web dispatcher... in that scenario do you still get the timeout? What I am getting at is that it might be the SAP Web Dispatcher (or some other link in the chain) sending back the timeout and not the SAP backend system - therefore the processing in SAP continues oblivious to the fact that a timeout has been sent to the client.

Cheers,

Simon