Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.7.11, 3.0
-
None
-
Unknown
Description
If a client doesn't read the entire message (maybe a fault is detected early) and closes the connection before the SoapOutInterceptor manages to write the body close/envelope close, a SOAPFault is thrown and then a whole series of log entries occurs from the original Fault, then a new fault due to trying to write out a new root (the SOAP:Fault element), etc...
We should detect if the cause is an EOFException and just ignore/continue as there is nothing we can do.