Forum Discussion

SiKing's avatar
SiKing
Community Hero
13 years ago

SoapUI testrunner fails to stop

I found this in SoapUI-Pro 4.6 on Win7, but suspect this existed for a while.

  1. in Windows launch the Task Manager, and select the Processes tab

  2. launch SoapUI - note it shows up in the Task Manager, note the PID

  3. select a testcase (or testsuite, does not matter)

  4. from the GUI, Launch TestRrunner and launch the selected test - note it shows up in the Task Manager, note the PID

  5. Cancel the TestRunner, dismiss all windows and exit SoapUI completely

  6. notice the PID of the TestRunner is still active; if you have selected a folder to export results, that folder is still locked by this process

    7. not good >:(

7 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    13 years ago
    If you on step 5 press the Cancel button the TestRunner process should be killed.
    After canceling the TestRunner do you got any messages in the soapUI log or error log (found in the bottom of the SoapUI window)?

    What kinds of tests are you running? Do you use any Groovy scripts in your tests?

    Regards
    Joel Jonsson
    SmartBear Sweden
  • SiKing's avatar
    SiKing
    Community Hero
    13 years ago
    There are no messages or errors in any of the logs. The _window_ stops and I am able to dismiss it normally. The _process_ does not stop as can be seen from the Windows Task Manager.
    I can reproduce this for any test involving any steps.
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    13 years ago
    Hi!

    We have been able to reproduce this issue now and I have added it to our issue tracker for prioritization (SOAP-631).
    The parent process (cmd) is killed when pressing cancel but not the java child process.

    Thanks for reporting this!

    Regards,
    Anders
    SmartBear Software
  • SiKing's avatar
    SiKing
    Community Hero
    13 years ago
    FYI: I have not tested this, but I believe this is a problem on Windows only. On *NIX (so Linux/Mac) if you kill the parent, the child also dies. Windows does not behave like this. Meaning that this needs to be handled differently on different platforms, else you will see some strange errors like "no such PID".
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    13 years ago
    Yes, you are correct. It seems to be windows only. I have verified that it is killed correctly in Linux.

    Regards,
    Anders
    SmartBear Software
  • SiKing's avatar
    SiKing
    Community Hero
    13 years ago
    Maybe you guys could arrange to have just Windows killed. >:D