NOTE: This article is 3 years or older so its information may no longer be relevant. Read on at your own discretion! Comments for this article have automatically been locked, refer to the FAQ
for more details.
Some of the recent work I've been doing required the use of SoapUI to do some basic load testing. When I first started this, every request I tried sending to the server was taking 30+ seconds to complete. This really stumped me because another, pretty much identical environment would respond immediately. I've finally tracked down the issue to DNS.
The environment I was trying to access was rarely used via SoapUI, so naturally I did not bother configuring its IP and hostname in the /etc/hosts
file. So I simply used the IP address for the web service endpoint I was accessing and thought that should be sufficient. It turns out, however, that SoapUI tries to do a DNS lookup on the IP address and as this was an internal address, the network name server would not respond for a long time. This is where the delay was coming from.
The solution was to add the IP address to the hosts file. The hostname doesn't actually matter in this case, it can be anything. Once this is done, SoapUI started establishing connections to the server instantly.
Hope you found this post useful...
...so please read on! I love writing articles that provide beneficial information,
tips and examples to my readers. All information on my blog is provided free of
charge and I encourage you to share it as you wish. There is a small favour I ask in return however -
engage in comments below, provide feedback, and if you see mistakes let me know.
If you want to show additional support and help me pay for web hosting and
domain name registration,
donations, no matter how small, are always welcome!
Use of any information contained in this blog post/article is subject to this disclaimer
Other posts you may like...