Testruns over WsdlTestCaseRunner lead to hanging JVM
If you start runs for individual testcases with
a RequestIconAnimator thread is started in the constructor of AbstractHttpRequest for each call to wsdlTestCaseRunner.run(). These thread are never closed, which means the JVM can not exit. The constructor of AbstractHttpRequest has the parameter "forLoadTest", which prevents starting the RequestIconAnimator if set to true, but this is not provided via WsdlTestCaseRunner.
A possible solution would be renaming the parameter to e.g. "forAPITest" and handing it down as true from WsdlTestCaseRunner or a suitable place down the line.
Workaround:
Setting the system property "java.awt.headless" to true also prevents the icon animator to be started:
But I'd better like a cleaner solution.
WsdlTestCaseRunner wsdlTestCaseRunner = new WsdlTestCaseRunner((WsdlTestCase) testCase, properties);
wsdlTestCaseRunner.run();
a RequestIconAnimator thread is started in the constructor of AbstractHttpRequest for each call to wsdlTestCaseRunner.run(). These thread are never closed, which means the JVM can not exit. The constructor of AbstractHttpRequest has the parameter "forLoadTest", which prevents starting the RequestIconAnimator if set to true, but this is not provided via WsdlTestCaseRunner.
A possible solution would be renaming the parameter to e.g. "forAPITest" and handing it down as true from WsdlTestCaseRunner or a suitable place down the line.
Workaround:
Setting the system property "java.awt.headless" to true also prevents the icon animator to be started:
System.setProperty("java.awt.headless", "true");
But I'd better like a cleaner solution.
