SoapUI 4.5.0 only uses 2 concurrent connections/sockets

Hello,

Sorry for the problem, we are looking into it.

robert
/Smartbear
[SOAPUI-3947]

Has there been any updates to this? When can we expect a fix for this?

This is a problem that is affecting me too and I have had several discussions with SmartBear support via email. One of our developers suggested that the problem could be related to the fact that SoapUI is using the Apache Soap Client and may be using this deprecated method: http://www.soapui.org/apidocs/com/eviware/soapui/impl/wsdl/support/http/SoapUIMultiThreadedHttpConnectionManager.html#setMaxConnectionsPerHost(int)


If you set these values then they may not be taking affect and the default is 2 connections.

The SmartBear contact suggested that this may indeed be the problem but I've received no further responses and the nightly builds of SoapUI (Pro in my case) have not resolved the issue.

Dave

Hi,

This has now been fixed in our internal builds, and a workaround has been published. Please see this post in the soapUI forum. Please continue discussion in that topic.

Regards

Henrik
SmartBear Software