TRFC Time limit exceeded issue

[Former Member]

We have issue about the TFC time limit exceeded. We have a third partner application which will call a HTTP service to our SAP, let's call the HTTP service as Z_submit_request, in Z_submit_request, we call RFC Z_process_request in IN BACKGROUND TASK, but we received a Time limit exceeded issue in SM58. Could anyone help to answer why we get this issue?

Thanks a lot!

[Former Member]

RFC's are executed in dialog tasks, which have an upper limit for the allowed runtime. This can be set for profile parameter rdisp/max_wprun_time. You might want to check the profile parameter (or ask the basis folks) if it has the default value (or another reasonable value). Most likely though I'd say you should look into the actual RFC and see if you can improve the performance of Z_PROCESS_REQUEST, so that the timeout doesn't occur.

[Former Member]

RFC's are executed in dialog tasks, which have an upper limit for the allowed runtime. This can be set for profile parameter rdisp/max_wprun_time. You might want to check the profile parameter (or ask the basis folks) if it has the default value (or another reasonable value). Most likely though I'd say you should look into the actual RFC and see if you can improve the performance of Z_PROCESS_REQUEST, so that the timeout doesn't occur.

[Former Member]

Thank you for your reply! Even we run the RFC in a backgroud task, there is still a time limit, right?

[Former Member]

All RFC's always run in a dialog task, not in background processes. You can trigger them so that they are processed asynchronously, but they still use dialog tasks and are thus also subject to the runtime limitations. So yes, despite the keyword BACKGROUND TASK the work process used for processing this task is a dialog process.

[Former Member]

Thank you very much!