cancel
Showing results for 
Search instead for 
Did you mean: 

Fiori oData Services - 500 Connection Timed Out

SandipAgarwalla
Active Contributor
0 Kudos

Hi All

How do we configure the time out parameters for the oData services in Gateway system?

Several of our Fiori oData services are getting timed out, some of these services take a while to fetch the data. Looks like the connection is timed out before the response is returned.

How are the connection time outs defined? Is it defined thru ICM Time out parameters?

Any help is appreciated.

Thanks

Sandip

Accepted Solutions (0)

Answers (1)

Answers (1)

AshwinDutt
Active Contributor
0 Kudos

Hello Sandip,

Please have a look here. It might help ->

Parameterization of the Gateway - Gateway - SAP Library

Timeout Parameters - Gateway - SAP Library

Regards,

Ashwin

kammaje_cis
Active Contributor
0 Kudos

Ashwin,

These links are not for Gateway-OData tool, rather it is a basis related component, which also unfortunately has the same name.

Sandip,

Yes, it is through profile parameters. If you have Web-Dispatcher as well, it will have its own parameters again. It is for the Basis team to configure it right. Check this link.

http://help.sap.com/saphelp_nw72/helpdata/en/48/88b52977323cb8e10000000a42189d/content.htm

Above is for the http timeout.


If the query is very inefficient, sql timeout can also happen. So you might have to relook the backend queries, since the default timeouts are getting exceeded and it is unusual.

Regards

Krishna

AshwinDutt
Active Contributor
0 Kudos

Hello Krishna,

Thank you for clarifying.

Regards,

Ashwin

SandipAgarwalla
Active Contributor
0 Kudos

Thanks Krishna

I guessed so, ICM parameters. So looks like the parameter which controls the time is icm/conn_timeout.

Its currently at 5000ms. What is a good number for the timeout.

We are obviously looking at fine tunning the backend query, but would be good to control the http timeouts.

Thanks

Sandip

kammaje_cis
Active Contributor
0 Kudos

5000ms, that is 5 seconds. That is a decent timeout parameter. If the user has to wait for more than 5 seconds then it may not be a great user experience. You can definitely try with more (say 8000ms).

I would do a trace on ICM as well as SQL(ST05) and check where the timeout is actually happening.