Forum Discussion

davideedle's avatar
11 years ago

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 to force quit.

I did not have this problem on the previous version.

Any thoughts about how to resolve this?

Thanks.

6 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    Hi,

    We have been trying to reproduce it on our end, but no luck. Just to avoid any room for misinterpretation can you try to write a bit detailed steps to reproduce. Also are you trying this for SOAP requests or REST requests?

    Regards,
    Shadid
    SmartBear Sweden.
  • imoraru's avatar
    imoraru
    New Contributor
    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.


    ...
    <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
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    Question to imoraru:

    Does this really happen to you when you create a blank testsuite? If not, it may be a different problem. When does it hang exactly?

    Best regards,
    Manne
  • imoraru's avatar
    imoraru
    New Contributor
    The sequence is:
    1. 'New Test Suite'. This works fine, it's created.
    2. 'New Test Case'. This is where it's hanging.

    Regards,
    Ion
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    That's very odd, I will try to reproduce the issue and post again in this forum as soon as I have some news for you.

    Best regards,
    Manne
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    I've now tried reproducing it without success. I also analyzed the source code, but as far as I can see we don't try to connect to the endpoints when we create a new test case (there shouldn't be any reason for it either).

    I tested it using the upcoming 4.6.1 version of SoapUI however. One important difference between the version is that we have now upgraded the Java runtime, which gives SoapUI support for Retina displays and also seems to improve stability considerably on Mac. Could you try again with the new version (should be released within a week) and see if you're still getting this crash?

    Kind regards,
    Manne Fagerlind