Thanks for the quick fix :)
On 2022/02/28 16:47:20 Rémy Maucherat wrote:
> Thanks for the test, this is what I had in mind. As I kind of expected
> when reading about the sequential technique used, the previous fix was
> causing a new problem since the thread id was not reset until the full
> recy
On Mon, Feb 28, 2022 at 4:39 PM Istvan SZEKELY
wrote:
>
> I've written a NonBlocking ReadWrite test (testDelayedNBReadWrite, in the
> attached file). I'm not sure if it is a valid test case (though works on
> 8.5.73, fails on 8.5.75). If it is valid, i can make a PR if needed.
Thanks for the te
I've written a NonBlocking ReadWrite test (testDelayedNBReadWrite, in the
attached file). I'm not sure if it is a valid test case (though works on
8.5.73, fails on 8.5.75). If it is valid, i can make a PR if needed.
On 2022/02/24 10:42:29 Rémy Maucherat wrote:
> On Thu, Feb 24, 2022 at 10:31 AM Is
On Thu, Feb 24, 2022 at 10:31 AM Istvan SZEKELY
wrote:
>
> Hello!
>
> I have an application where a ReadListener and a WriteListener (call it
> MyWriteListener) set to the ServletInputStream and the ServletOutputStream
> objects. Updating the Tomcat container from 8.5.73 to 8.5.75, the follow
> er
Hello!
I have an application where a ReadListener and a WriteListener (call it
MyWriteListener) set to the ServletInputStream and the ServletOutputStream
objects. Updating the Tomcat container from 8.5.73 to 8.5.75, the follow
error occured. The ServletOutputStream objects's isReady function alway
