Strange Behavior With Network Connections
I've done several searches for this and haven't come up with anything for my problem.
When I start up soapUI, everything appears to be working as they should. However, when I execute something that requires using the network, it just sits there with the "progress bar" moving. It's not stalled out/frozen. I can cancel the request, save and close, etc. It's just when I try to perform an action that uses the network (update WSDL definition from network, send a SOAP request to a server, etc)
I have left it running in this strange state, and about an hour later, it finally hits the network and finishes the request. From then on, I don't see any problems. It responds like a champ. Requests will take about 36ms from then on. The problem I'm seeing appears to only happen when first starting soapUI.
I have tried different versions of Java (Sun 1.5 and different updates from 1.6, and even an IBM 1.5 JRE). It's the same on all of them. I've even downoaded different versions of soapUI. I even see this same problem when using soapUI as an Eclipse plugin.
I've done the obvious of making sure I don't have a firewall running on my machine. I've also made sure that network connections aren't going through any proxies and am using a "direct connection" I'm hitting localhost (even tried 127.0.0.1 to avoid any chance of DNS lookup timeouts), so I am unsure what is causing this hang up.
The reason I'm putting this post in this forum is because soapUI is the only Java application I'm seeing this behavior with.
Any suggestions would be greatly appreciated. Getting soapUI to respond quickly at startup would be a big time saver.
When I start up soapUI, everything appears to be working as they should. However, when I execute something that requires using the network, it just sits there with the "progress bar" moving. It's not stalled out/frozen. I can cancel the request, save and close, etc. It's just when I try to perform an action that uses the network (update WSDL definition from network, send a SOAP request to a server, etc)
I have left it running in this strange state, and about an hour later, it finally hits the network and finishes the request. From then on, I don't see any problems. It responds like a champ. Requests will take about 36ms from then on. The problem I'm seeing appears to only happen when first starting soapUI.
I have tried different versions of Java (Sun 1.5 and different updates from 1.6, and even an IBM 1.5 JRE). It's the same on all of them. I've even downoaded different versions of soapUI. I even see this same problem when using soapUI as an Eclipse plugin.
I've done the obvious of making sure I don't have a firewall running on my machine. I've also made sure that network connections aren't going through any proxies and am using a "direct connection" I'm hitting localhost (even tried 127.0.0.1 to avoid any chance of DNS lookup timeouts), so I am unsure what is causing this hang up.
The reason I'm putting this post in this forum is because soapUI is the only Java application I'm seeing this behavior with.
Any suggestions would be greatly appreciated. Getting soapUI to respond quickly at startup would be a big time saver.
