Yes - the same situation occurs on another machine. The steps to reproduce is:
1. Get SoapUI zip version 4.0.1
2. Create Java project (in Eclipse)
3. Add "lib" jars from SoapUI archive and the main soapui-4.0.1.jar
4. Create a new class with
public static void main() method. WARNING: using a static main method is extremely important. Using a
test JUnit method will not do.
5. Create a new SoapUITestCaseRunner
6. Run the Java application
7. Observe the application not stopping
import com.eviware.soapui.tools.SoapUITestCaseRunner;
public class SoapUiTest {
public static void main(String[] args) {
new SoapUITestCaseRunner();
}
}
Debugging the code appears to be leaving two threads running:
- Thread [Timer-0] (Running)
- Thread [DestroyJavaVM] (Running)
Obviously there is some Timer left behind.