LoadUI Running out of TCP Connections

Hello,

We are trying to us LoadUI to do some load testing of a web service. The call and response work fine in SoapUI, and at first worked ok in LoadUI, but for some reason, we can't get it to run for any length of time in LoadUI. (Background, this is trying to run on both a Windows XP and Windows 7 machine). What happens is, the load test runs, then will start generating errors indicating that it can't open any more connections. I found the error log, and it's full of these:

2012-05-17 12:35:33,811 ERROR [WsdlSubmit] Exception in request: java.net.BindException: Address already in use: connect
2012-05-17 12:35:33,811 ERROR [errorlog] java.net.BindException: Address already in use: connect
java.net.BindException: Address already in use: connect
 at java.net.TwoStacksPlainSocketImpl.socketConnect(Native Method)
 at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
 at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
 at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
 at java.net.PlainSocketImpl.connect(Unknown Source)
 at java.net.SocksSocketImpl.connect(Unknown Source)
 at java.net.Socket.connect(Unknown Source)
 at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:123)
 at com.eviware.soapui.impl.wsdl.support.http.SoapUIMultiThreadedHttpConnectionManager$SoapUIClientConnectionOperator.openConnection(SoapUIMultiThreadedHttpConnectionManager.java:299)
 at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:149)
 at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:121)
 at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:561)
 at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:415)
 at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
 at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
 at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$Helper.execute(HttpClientSupport.java:217)
 at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport.execute(HttpClientSupport.java:328)
 at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:251)
 at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:123)
 at com.eviware.soapui.impl.wsdl.WsdlSubmit.submitRequest(WsdlSubmit.java:76)
 at com.eviware.soapui.impl.wsdl.WsdlRequest.submit(WsdlRequest.java:238)
 at com.eviware.soapui.impl.wsdl.teststeps.WsdlTestRequestStep.run(WsdlTestRequestStep.java:407)
 at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:238)
 at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runCurrentTestStep(WsdlTestCaseRunner.java:48)
 at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:147)
 at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:42)
 at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:135)
 at com.eviware.loadui.components.soapui.SoapUISamplerComponent$SoapUITestCaseRunner.run(SoapUISamplerComponent.java:1160)
 at com.eviware.loadui.components.soapui.SoapUISamplerComponent.sample(SoapUISamplerComponent.java:991)
 at com.eviware.loadui.impl.component.categories.RunnerBase.doSample(RunnerBase.java:506)
 at com.eviware.loadui.impl.component.categories.RunnerBase.access$700(RunnerBase.java:67)
 at com.eviware.loadui.impl.component.categories.RunnerBase$Worker.run(RunnerBase.java:765)
 at com.eviware.loadui.util.dispatch.CustomThreadPoolExecutor$Worker.run(CustomThreadPoolExecutor.java:197)
 at java.lang.Thread.run(Unknown Source)

I'm attaching a screenshot of the LoadUI project. It's just a scheduler, a Fixed Load component, and a SoapUI runner.

Thanks for any help you can give, this error is preventing us for debugging some crashing behavior in our web service (the "bad connections" error happens way before the web server has issues, or even if the service doesn't crash.)

Thanks.