on 12-02-2009 10:43 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 in the RFC ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
you can use a timer control and make some test request every 10 minutes.
This is the best way I've ever known.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.