Forum Discussion
SmartBear_Suppo
15 years agoSmartBear Alumni (Retired)
Hi!
this error occurs if soapUI is unable to match the incoming request to any of the defined Mock Operations (which it does using the underlying WSDL definition). In these two cases:
1) Looks correct; can you attach a soapUI Project that we could use to reproduce this? (ie with the WSDL, MockService and request)
2) Judging from the error message the request is not a valid SOAP request; can you somehow log it (or run your requests through the HTTP Monitor) so you can see exactly what is being sent?
regards!
/Ole
eviware.com
this error occurs if soapUI is unable to match the incoming request to any of the defined Mock Operations (which it does using the underlying WSDL definition). In these two cases:
1) Looks correct; can you attach a soapUI Project that we could use to reproduce this? (ie with the WSDL, MockService and request)
2) Judging from the error message the request is not a valid SOAP request; can you somehow log it (or run your requests through the HTTP Monitor) so you can see exactly what is being sent?
regards!
/Ole
eviware.com
- MatthiasBuck10 years agoOccasional Contributor
I noticed that this error also shows when you have two Mock Response steps serving the same Port/URL even though only one is enabled (not disabled). When I delete the disabled step, it works fine.
When I hit the URL with ?wsdl at the end, I can see the running services.
Another problem is, when I stop the test cases and restart them, more and more running services with the same endpoint get added.
Here is what the server shows me when using my URL with ?wsdl attached to the end of it.
There are currently 4 running SoapUI MockServices
- NotificationSvc
- SOAP Mock Response
- SOAP Mock Response
- SOAP Mock Response
Related Content
- 10 years ago
- 11 years ago
- 11 years ago
- 5 years ago
Recent Discussions
- 4 hours ago
- 26 days ago