SoapUI endpoint error in random order

I do not understand anything about SoapUI and its Muscovites. I am using SoapUI client (testcase) and Java EE application with JAX-RPC.

My problem:

when I try to call any web service from my Java client or SoapUI test file, the mockservice returns a well message on the first call and an error below on the second call with the same call or not. But if I wait, it works ...

So, I have included this option in SOAPui: "Close the HTTP connection after each SOAP request", and it works all the time ...

So my question is:

" This is normal mockservice behavior and how to implement this with my java client? "

Thanks to everyone.

<soapenv:Fault> <faultcode>Server</faultcode> <faultstring>Missing operation for soapAction [] and body element [null] with SOAP Version [SOAP 1.1]</faultstring> </soapenv:Fault> 
+6
source share
3 answers

OK, I found a solution on the SoapUI forum: http://www.soapui.org/forum/viewtopic.php?t=5648

This is when you have the "HTTP Settings / Logs wire content of all mock requests" settings flag set to true. => Uncheck the box and it works great!

+7
source

Thanks a lot!

I had the same problem using SoapUI 5.1.2 Pro. After receiving the first asynchronous response to the MockService, the MockService stopped and could not get more answers to the request you sent. Error message: Thu Jul 02 12:59:44 CEST 2015: ERROR: An error occurred [There is no operation for soapAction [XXXX] and body element [null] with SOAP version [SOAP 1.1]], see Error log for details

In SoapUI settings: File-> Preferences-> Http Settings: "Enable Mock HTTP Log", uncheck the box: "Records the contents of the posting in all false requests."

Now I get some asynchronous responses in a line and return them back.

+4
source

The same problem can occur when two mock services work with the same endpoint address (including port and path) in SoapUI.

0
source

All Articles