cancel
Showing results for 
Search instead for 
Did you mean: 

SAP MDK Service timeout

0 Kudos
431

Hi,

I have an SAP MDK app that consumes a service and it’s deployed both on Mobile services and on Cloud Foundry.

I’m getting an issue, mainly on the web version, where some service calls are going through the the service but take a long time to return and the app throws an error despite the call being correctly made on the service.

Is there a way to increase the timeout time for the service calls?

Thank you in advance.

Best Regards

Nuno Oliveira

Accepted Solutions (1)

Accepted Solutions (1)

mingkho
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Nuno,

Can you confirm this: the long time to return from the service is expected and you are just looking for way to increase the request timeout?

MDK is using XMLHttpRequest for the underlying request and the default timeout is 0 which means there's not timeout at all.

Can you provide more details on the issue? how long was it until you get the timeout error? and what error did you get?

You can also check the browser DevTools' Console and Network tabs to see what's the returned error and check if the timeout is perhaps coming from server?

Regards

Ming

0 Kudos

Hi Ming,

To be honest the timeout is just a suspicion since it happened in a client device, nothing abnormal was found on the backend logs and the request as placed correctly on the service.

I’m planning on doing a session with the client with all the tracings to validate that, but since it is expected that the client will have bad connection in some occasions we wanted to check the timeouts anyway.

Could it be that the cloud foundry is the one to send the timeout?

Best Regards

Nuno

mingkho
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Nuno

Without more details on the error, it's hard to tell where it could come from. So I'd definitely suggest getting more details on the error on client side and which action the error occurred on.

Regards

Ming

0 Kudos

Hi Ming,

We can’t replicate the issue anymore so we’ve put this issue on hold. I’ll increase the logging coverage for this functionality in case it happens in the future.

Thank you for the help.

Nuno Oliveira

Answers (0)