I am getting the same thing. I have just loaded the latest build and although the documentation descirbes many fixes to the software, this is not one of them.
We have been using SOAPUI for years and this is a new problem. Here are my specifics and observations.
1 - Latest build.
2- Windows 7 Pro, 64 bit everything.
3- WSDL's being served by a local version of TomCat (i.e. wsdl path:
http://localhost:8080/somepath/somewsdl)
Observationsl.
When the WSDL's are loaded from the file system there is no problem. Same WSDL's via the local server and you get random stoppage of the import.
If you fire up a stand alone instance of TCPMON, the imports will work.
If you try the same WSDL repeatedly, you will see in the logs that the schema data stops coming in at different points, all of which are not EOF.
TomCat reports no errors and will return complete files every time (tested using other means).
Popup error: Error loading [http://localhost:8080/WebISSA/ISSA_5.0_schemas/common/collections.xsd]: java.net.SocketTimeoutException: Read timed out
Error:
Thu May 17 11:44:39 EDT 2012:ERROR:com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException
com.eviware.soapui.impl.support.definition.support.InvalidDefinitionException
at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlLoader.loadXmlObject(WsdlLoader.java:138)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:535)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.selectDefinitionParts(SchemaUtils.java:565)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:547)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.selectDefinitionParts(SchemaUtils.java:565)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:547)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.selectDefinitionParts(SchemaUtils.java:565)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:547)
at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.getDefinitionParts(SchemaUtils.java:524)
at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionCache.update(AbstractDefinitionCache.java:97)
at com.eviware.soapui.impl.support.definition.support.AbstractDefinitionContext$Loader.construct(AbstractDefinitionContext.java:226)
at com.eviware.soapui.support.swing.SwingWorkerDelegator.construct(SwingWorkerDelegator.java:46)
at com.eviware.soapui.support.swing.SwingWorker$2.run(SwingWorker.java:149)
at java.lang.Thread.run(Unknown Source)
Last Line in the Http log when trying to import the same WSDL/schemas repeatedly. NOTE: This is not what is in the file. The file is valid.
try 1: Thu May 17 11:43:39 EDT 2012:DEBUG:<< " <xsd:element name="targetC"
try 2: Thu May 17 12:05:01 EDT 2012:DEBUG:<< "<xsd:element name="internationa"
try 3: Thu May 17 12:06:19 EDT 2012:DEBUG:<< " <xsd:element name="
<started tcpmon (external to soapui)>
try 4: Continued much further then stopped again. Never did this before. Other wsdls worked in this case. Same error, different spot
Thu May 17 12:07:58 EDT 2012:DEBUG:<< "[0x9]<!-- ==========="
try 5: Same file, from disk - Success.
What we are doing is not new and has worked with previous versions of SOAPUI.
Best guess: Timing/chunking issue.