[undertow-dev] keep-alive?

Stuart Douglas sdouglas at redhat.com
Tue Jun 4 18:23:13 EDT 2013


np, you had me worried for a minute there :-)

Stuart

Bill Burke wrote:
> Nevermind.  Stupid fucking TCK is closing HttpClient and then trying to
> read the response.
>
> On 6/4/2013 9:54 AM, Bill Burke wrote:
>> I'll get you a simple test case.
>>
>> On 6/3/2013 6:41 PM, Stuart Douglas wrote:
>>> It should support Keep-Alive. This sounds like a bug. Is there any easy
>>> way for me to reproduce?
>>>
>>> If not, is there any chance you could send me a wireshark dump so I can
>>> see exactly what is going over the wire?
>>>
>>> In general Undertow will only close the connection prematurely when
>>> something corrupts the stream to the point where it cannot continue
>>> (e.g. setting a content-length of 100 then only writing 50).
>>>
>>> Stuart
>>>
>>> Bill Burke wrote:
>>>> Does undertow support keep-alive yet?  I'm using Apache HC Client 4.2.1
>>>> and am getting a "ConnectionManager has been shutdown" exception after
>>>> trying to read a 0 length response body from a 200, ok status.  So it
>>>> seems that Undertow is closing the connection after the response returns.
>>>>
>>>> Before you say, "well don't read from a 0 length response", the JAX-RS
>>>> 2.0 spec requires that we throw a certain exception on an empty response
>>>> when trying to read an actual response.  Undertow is setting a
>>>> Content-Length of "0", so I can workaround this problem by checking for
>>>> this condition, but closing the connection isn't really great for
>>>> performance....
>>>>
>>>>
>


More information about the undertow-dev mailing list