SOAPUI 4.6.0 hangs when adding testcases
I upgraded to 4.6.0 (am on Mac OSX10.7.4). I can created a blank TestSuite, but when I try to add a Request to a TestSuite, I answer all the prompts with defaults, and then soapUI hangs and I have ...
Forum Discussion
I had the same issue. It seems to me that it's hanging when the site it's trying to connect is not available.
In my case, I used SOAP calls and the initial definition was loaded from an URL that was not available any more when I was trying to add the test case (working from a different location).
To fix it I have changed the service endpoint definition to an URL that was accessible and updated all the requests. Still no luck.
The only way I got it to work is to open the SOAPUI project file in an editor and change the URLs at the end of the file to point to sites that were accessible.
I changed them all to the 192 address that was accessible.
Same happened to me when I was trying to bring up SOAPUI while on a customer site where I have limited internet access.
It won't get past the start page. The only way I could make it work is to disconnect all network interfaces and bring up SOAPUI. The start page complains but you can use the tool afterwards (if you update the URLs).
Hope this helps
Ion
In my case, I used SOAP calls and the initial definition was loaded from an URL that was not available any more when I was trying to add the test case (working from a different location).
To fix it I have changed the service endpoint definition to an URL that was accessible and updated all the requests. Still no luck.
The only way I got it to work is to open the SOAPUI project file in an editor and change the URLs at the end of the file to point to sites that were accessible.
...
<con:endpointStrategy xsi:type="con:DefaultEndpointStrategy" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><con:endpoint mode="COMPLEMENT" username="xx" password="xx">http://192.168.0.123:8011/tnp-ws/services</con:endpoint><con:endpoint mode="COMPLEMENT" username="xx" password="xx">http://17.153.109.89:8011/tnp-ws/services</con:endpoint><con:endpoint mode="COMPLEMENT" username="xx" password="xx">http://215.183.89.147:8011/tnp-ws/services</con:endpoint></con:endpointStrategy><con:properties/><con:wssContainer/><con:sensitiveInformation/></con:soapui-project>
I changed them all to the 192 address that was accessible.
Same happened to me when I was trying to bring up SOAPUI while on a customer site where I have limited internet access.
It won't get past the start page. The only way I could make it work is to disconnect all network interfaces and bring up SOAPUI. The start page complains but you can use the tool afterwards (if you update the URLs).
Hope this helps
Ion
