Hi Oleg, Roland
Thanks for your prompt responses..
The 'connection: close' header is added by the ResponseConnControl
protocol interceptor [1]. In many cases 500 status code represents a
fatal error, which may leave the connection in an inconsistent state.
Therefore, I think it is a reasonable defensive measure to drop the
connection.
Do you want this changed?
Since we are dealing with SOAP messages, the SOAP spec states that a
SOAP fault should be in a response with a HTTP 500 error. In our case
this does not mean that anything is messed up with the HTTP connection.
The point that makes me think something is not right is that this causes
the 'Response already committed' error - whereas when load testing with
non-error replies, things are fine. Let me look at the protocol
interceptor and get back to you on this
thanks
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
