topic Re: Setting timeout in Application Development and Automation Discussions

Setting timeout

Former Member — Mon, 13 Jun 2005 22:26:09 GMT

Hi all,

I'm making a long series of BAPI calls, and about six minutes in we get the error "connection closed without message (CM_NO_DATA_RECEIVED)". I would think this is some kind of timeout problem, except it fails at the same spot nine minutes in running on a slower system. Also, if I remove some calls, it fails at a different spot.

Are there some timeout settings we can check out on the R3 system? What else might this be?

Thanks.

Re: Setting timeout

nishanthbhandar — Tue, 14 Jun 2005 06:30:33 GMT

Hi Sansanee,

The default length of the connection time-out is set in the system profile in the parameter rspo/tcp/timeout/connect.

You can set the number of retries of a failed connect or read/write operation using the system profile parameter rspo/tcp/retries. You can specify how long the system should wait between retries using the parameter rspo/tcp/retrytime.

Cheers

Nishanth