Re: Tomcat 9.0 async read becomes blocking with chunked transfer-encoding
Thank you Mark Andrew > On Oct 8, 2021, at 1:44 AM, Mark Thomas 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 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-unsubscr...@tomcat.apache.org >>> For additional commands, e-mail: users-h...@tomcat.apache.org >>> >> - >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org > > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
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 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-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 9.0 async read becomes blocking with chunked transfer-encoding
Mark, Thank you very much for the quick fix Andrew > On Sep 27, 2021, at 8:54 AM, Mark Thomas 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-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 9.0 async read becomes blocking
Hi Chris,
Servlet 3.1 spec defines that ServletInputStream can be used to read as
non-blocking way as long as there is data ready locally by calling isReady
method and check the ready condition before calling read, and read should throw
IllegalStateException if called by caller when data is not ready
Agree that InputStream read api is blocking by nature, but if the data is
already there in local buffer, then it’s not, it’s just exposing as
ServletInputStream
https://javaee.github.io/servlet-spec/downloads/servlet-3.1/Final/servlet-3_1-final.pdf
> On Sep 21, 2021, at 2:26 PM, Christopher Schultz
> wrote:
>
> Andrew,
>
>> On 9/21/21 13:54, Javateck wrote:
>> Hi,
>> With NIO connector with Servlet 3.1 support, I’m registering with a
>> ReadListener, while it got the first read signal from tomcat container (I
>> tried 9.0.19 and 9.0.53), the read call is blocked after isReady returns true
>> if (ServletInputStream.isReady()) {
>>ServletInputStream.read(buffer); // this becomes blocking
>> }
>> I tried with jetty, it’s working fine
>> When I did the test, I was holding the sending packet from client side
>> Not sure whether anyone has tried this
>
> InputStream is always blocking.
>
> Are you trying to use async? That's not the way to use async...
>
> -chris
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
Re: Tomcat 9.0 async read becomes blocking
It’s happening in chunk encoding
> On Sep 21, 2021, at 10:54 AM, Javateck wrote:
>
> Hi,
>
> With NIO connector with Servlet 3.1 support, I’m registering with a
> ReadListener, while it got the first read signal from tomcat container (I
> tried 9.0.19 and 9.0.53), the read call is blocked after isReady returns true
>
> if (ServletInputStream.isReady()) {
> ServletInputStream.read(buffer); // this becomes blocking
> }
>
> I tried with jetty, it’s working fine
>
> When I did the test, I was holding the sending packet from client side
>
> Not sure whether anyone has tried this
>
> Thanks,
> Andrew
>
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Tomcat 9.0 async read becomes blocking
Hi,
With NIO connector with Servlet 3.1 support, I’m registering with a
ReadListener, while it got the first read signal from tomcat container (I tried
9.0.19 and 9.0.53), the read call is blocked after isReady returns true
if (ServletInputStream.isReady()) {
ServletInputStream.read(buffer); // this becomes blocking
}
I tried with jetty, it’s working fine
When I did the test, I was holding the sending packet from client side
Not sure whether anyone has tried this
Thanks,
Andrew
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
