hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oleg Kalnichevski <ol...@apache.org>
Subject Re: Response already committed error when sending error responses on a load test
Date Sun, 14 Oct 2007 16:30:15 GMT
On Sun, 2007-10-14 at 18:22 +0200, Roland Weber wrote:
> Hi Oleg,
> 
> > 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.
> 
> The connection itself should be in a consistent state, since it
> is used to send an error response. I can imagine that the response
> object may be in an inconsistent state. But then it should not be
> used for sending the response in the first place, right?
> 
> > Therefore, I think it is a reasonable defensive measure to drop the
> > connection.
> 
> I can live with that. But maybe we should discuss where exactly
> inconsistencies may occur, and whether dropping the connection
> helps to solve them.
> 

While the connection itself may still be re-usable, the associated
execution context gets messed up to a point, that it simply makes no
sense to keep the connection alive.

Oleg 


> cheers,
>   Roland
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: httpcomponents-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpcomponents-dev-help@jakarta.apache.org


Mime
View raw message