Enable Mock HTTP Log - Session Weirdness
Environment: soapUI version 4.5.1, Windows 7 and OSx
Enabling mock http logging causes subsequent WS calls to fail. If differing WS requests are dispatched to the Mock in short order (< 5sec) the mock returns with the following response:
This also happens if 'Close connections after request' is enabled ! It doesn't matter what kind of service request is sent to what service on the Mock the fault is always the same. Once http logging is switched off, the Mock works as expected.
The observed behavior can be reproduced with any web client and even the soapUI internal TestSuits.
Enabling mock http logging causes subsequent WS calls to fail. If differing WS requests are dispatched to the Mock in short order (< 5sec) the mock returns with the following response:
<soapenv:Body>
<soapenv:Fault>
<faultcode>Server</faultcode>
<faultstring>Missing operation for soapAction [] and body element [null] with SOAP Version [SOAP 1.1]</faultstring>
</soapenv:Fault>
</soapenv:Body>
This also happens if 'Close connections after request' is enabled ! It doesn't matter what kind of service request is sent to what service on the Mock the fault is always the same. Once http logging is switched off, the Mock works as expected.
The observed behavior can be reproduced with any web client and even the soapUI internal TestSuits.
