Forum Discussion
juandid
16 years agoOccasional Contributor
It is unbelievable. Based on a discussion I found on the internet I decided to test with tomcat 6 instead of 5. Now I verified using a tomcat 6.0.29 instead of 5.5.23. The java.net.ConnectException has gone. I can access the mock service from nettool as well as from soapUI.
So this issue is solved.
So this issue is solved.
