2009 Dec 02 10:40 PM
I have a WD application which calls an RFC. If the RFC is not completed within five minutes. The WD application gets a Time_Out dump screen on web browser. This is because the parameter icm/keep_alive_timeout is set to 300 seconds.
I am trying to prevent the dump screen by tracking the elapsed runtime of RFC and exiting before the 300seconds, i.e.: 280 and giving the user an error message that there was a timeout.
My question is whether there is a more sophisticated way to capture the Time_Out? It is not a class exception, so how would I capture this event?
I have a WD application which calls an RFC. If the RFC is not completed within five minutes. The WD application gets a Time_Out dump screen on web browser. This is because the parameter icm/keep_alive_timeout is set to 300 seconds.
I am trying to prevent the dump screen by tracking the elapsed runtime of RFC and exiting before the 300seconds, i.e.: 280 and giving the user an error message that there was a timeout.
My question is whether there is a more sophisticated way to capture the Time_Out? It is not a class exception, so how would I capture this event?
2009 Dec 03 5:34 AM
Hi Raynald,
There is a class cl_gui_timer which is used for this kind of scenarios. Check if this helps you in anyway.
Also search with cl_gui_timer in sdn, may be it gives you some more information.
Regards,
Swarna Munukoti.
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |