2017 Oct 02 5:09 PM
Dear ABAP Fellows 🙂
Is there a reliable way to enforce a time out for a parallel task started using:
CALL FUNCTION .... STARTING NEW TASK
Let say I want to start 3 parallel tasks with different time outs:
Task 1 - 10 seconds
Task 2 - 20 seconds
Task 3 - 30 seconds
Any suggestions how to achieve this?
Thanks,
Jacek
2018 Feb 09 2:39 PM
Sorry for the long inactivity in the topic. I couldn't find a solution until just recently.
WAIT UNTIL command is just a part of the solution as the started tasks will continue to run in the background (even after the parent program finishes).
To terminate them (and free up resources) function module RFC_CONNECTION_CLOSE should be called passing task name as a parameter (task name as specified in CALL FUNCTION...STARTING NEW TASK taskname).
Thank you for the hint!
Dear ABAP Fellows 🙂
Is there a reliable way to enforce a time out for a parallel task started using:
CALL FUNCTION .... STARTING NEW TASK
Let say I want to start 3 parallel tasks with different time outs:
Task 1 - 10 seconds
Task 2 - 20 seconds
Task 3 - 30 seconds
Any suggestions how to achieve this?
Thanks,
Jacek
2017 Oct 02 9:48 PM
2018 Feb 09 2:39 PM
Sorry for the long inactivity in the topic. I couldn't find a solution until just recently.
WAIT UNTIL command is just a part of the solution as the started tasks will continue to run in the background (even after the parent program finishes).
To terminate them (and free up resources) function module RFC_CONNECTION_CLOSE should be called passing task name as a parameter (task name as specified in CALL FUNCTION...STARTING NEW TASK taskname).
Thank you for the hint!
2018 Feb 09 2:52 PM
I have tried to find out if/how ABAP unit tests execution time is limited. I found Class CL_AUNIT_CLASSTEST_SESSIONFE, Method __CANCEL_RFC does what you are proposing.
I will try to replicate it.
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |