You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Javateck <ja...@gmail.com> on 2021/10/07 21:23:54 UTC
Re: Tomcat 9.0 async read becomes blocking with chunked transfer-encoding
Hi Mark,
Just wondering whether we have a radar to track this, will it be in release notes for next release?
Thanks,
Andrew
> On Sep 27, 2021, at 8:54 AM, Mark Thomas <ma...@apache.org> wrote:
>
> On 27/09/2021 15:55, Mark Thomas wrote:
>>> On 27/09/2021 09:08, Goldengate liu wrote:
>>> Hi Mark,
>>>
>>> I’m uploading some test files
>> Thanks for the test case. I'm looking at this now.
>
> Bug found and fixed.
>
> One thing to note is that with chunked encoding it is possible for you to see isReady() return true only for the subsequent read to return 0 bytes. This happens when just (or only part of) the chunked header is available.
>
> The sample code you provided handled this correctly.
>
> The fix will be in the October release round. The release process for that should hopefully start later today.
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 9.0 async read becomes blocking with chunked transfer-encoding
Posted by Javateck <ja...@gmail.com>.
Thank you Mark
Andrew
> On Oct 8, 2021, at 1:44 AM, Mark Thomas <ma...@apache.org> wrote:
>
> On 07/10/2021 22:23, Javateck wrote:
>> Hi Mark,
>> Just wondering whether we have a radar to track this, will it be in release notes for next release?
>
> The fix is in 9.0.54 and is listed in the changelog.
>
> Mark
>
>> Thanks,
>> Andrew
>>>> On Sep 27, 2021, at 8:54 AM, Mark Thomas <ma...@apache.org> wrote:
>>>
>>> On 27/09/2021 15:55, Mark Thomas wrote:
>>>>> On 27/09/2021 09:08, Goldengate liu wrote:
>>>>> Hi Mark,
>>>>>
>>>>> I’m uploading some test files
>>>> Thanks for the test case. I'm looking at this now.
>>>
>>> Bug found and fixed.
>>>
>>> One thing to note is that with chunked encoding it is possible for you to see isReady() return true only for the subsequent read to return 0 bytes. This happens when just (or only part of) the chunked header is available.
>>>
>>> The sample code you provided handled this correctly.
>>>
>>> The fix will be in the October release round. The release process for that should hopefully start later today.
>>>
>>> Mark
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat 9.0 async read becomes blocking with chunked
transfer-encoding
Posted by Mark Thomas <ma...@apache.org>.
On 07/10/2021 22:23, Javateck wrote:
> Hi Mark,
>
> Just wondering whether we have a radar to track this, will it be in release notes for next release?
The fix is in 9.0.54 and is listed in the changelog.
Mark
>
> Thanks,
> Andrew
>
>> On Sep 27, 2021, at 8:54 AM, Mark Thomas <ma...@apache.org> wrote:
>>
>> On 27/09/2021 15:55, Mark Thomas wrote:
>>>> On 27/09/2021 09:08, Goldengate liu wrote:
>>>> Hi Mark,
>>>>
>>>> I’m uploading some test files
>>> Thanks for the test case. I'm looking at this now.
>>
>> Bug found and fixed.
>>
>> One thing to note is that with chunked encoding it is possible for you to see isReady() return true only for the subsequent read to return 0 bytes. This happens when just (or only part of) the chunked header is available.
>>
>> The sample code you provided handled this correctly.
>>
>> The fix will be in the October release round. The release process for that should hopefully start later today.
>>
>> Mark
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org