Forum Discussion
I did the same test on another machine (also Windows Server 2012 R2) and it worked (see the log below).
When I compare the logs of both tests I see a small difference.
Working:
Sending request: POST /mockServiceSoapBinding HTTP/1.1
Not working:
Sending request: POST http://127.0.0.1:8088/mockServiceSoapBinding HTTP/1.1
Why does SoapUI use the host addres (http://127.0.0.1:8088) on the machine where the tutorial doesn't work?
How can I tell SoapUI that it must not use the host address?
SoapUI log:
Sat Sep 12 18:43:09 CEST 2015:DEBUG:Attempt 1 to execute request
Sat Sep 12 18:43:09 CEST 2015:DEBUG:Sending request: POST /mockServiceSoapBinding HTTP/1.1
Sat Sep 12 18:43:10 CEST 2015:DEBUG:Receiving response: HTTP/1.1 200 OK
Sat Sep 12 18:43:10 CEST 2015:DEBUG:Connection can be kept alive indefinitely
Sat Sep 12 18:43:10 CEST 2015:INFO:Got response for [ServiceSoapBinding.login:login rq] in 247ms (283 bytes)
Sat Sep 12 18:43:40 CEST 2015:DEBUG:Connection closed
- nmrao10 years agoChampion Level 3I believe that mock service run on the same machine as you start it from soapui
- groof10 years agoNew Contributor
The mock service and soapui run on the same machine. Because it didn't work I performed the same test on another machine (also Windows Server 2012 R2) and there it worked. I realy don't know why it failed on the first machine. On both machines I performed the same steps:
- Downloaded SoapUI 5.2.0 and install it on a Windows Server 2012 R2 machine
- Import Sample SOAP Project Core
- Generate New SOAP MockService
- Start the ServiceSoapBinding MockService
- Open login rq and submit request
- groof10 years agoNew Contributor
Problem solved by setting "SoapUI Preferences | Proxy Settings" to "None".
Related Content
Recent Discussions
- 15 years ago
- 12 days ago