Stopping running RFT script from RQM web interface
Does anyone have detailed knowledge of the sequence of events involved in stopping a running Rational Functional Tester script from the Rational Quality Manager web interface ? What I assume happens is that the RQM server somehow uses the RFT adapter to send some sort of message or signal to the RFT Java process. What we are seeing is that, having clicked the button in the web interface there is often a lengthy delay before the RFT Java process terminates. Furthermore we've found that simply by introducing sleep() calls into the Java code this allows the RFT Java process to be terminated more quickly in response to clicking stop in the web interface.
3 answers
Hi Paul,
The RFT adapter contacts RQM server after some polling interval (normally 5 sec.) to check, if RQM has any job for it. RQM server never contacts to any adapter.
When you click on the "Stop Run" button in the RQM web UI, RQM generates "Stop Execution" request for the adapter. When adapter next time contacts RQM server, RQM sends the request to the adapter and adapter send the stop request to the RFT tool to stop the ongoing execution.
So the time required to stop the execution depends on the adapter's polling interval and the network latency.
Hope this is helpful.
Thanks,
Vijay.