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

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

Re: Tomcat SSL - Issue

Another way you get supported is TLS and the cipher suite. nmap -sV --script ssl-enum-ciphers -p nmap -sV --script ssl-enum-ciphers -p On Tue, Sep 21, 2021 at 5:25 PM Christopher Schultz < ch...@christopherschultz.net> wrote: > Priyanka, > > On 9/21/21 13:52, Kumawat,

RE: Max outbound requests setting in Tomcat 9.X

Chandra, > -Original Message- > From: Gullapalli, Chandra Mouli > Sent: Tuesday, September 21, 2021 3:32 PM > To: users@tomcat.apache.org > Subject: Max outbound requests setting in Tomcat 9.X > > Hi, > > I know that we can set restrictions on the number of incoming requests to a >

Max outbound requests setting in Tomcat 9.X

Hi, I know that we can set restrictions on the number of incoming requests to a Tomcat server. However if tomcat has to make an outbound http it has only max limit of 2 http outbound requests? Is there a way to increase the limit of max number of outbound requests from a tomcat server to an

Re: JASPIC AuthConfigProvider packaged with the web application not found

Hi, Am 19.09.21 um 19:48 schrieb Keil, Matthias (ORISA Software GmbH): Hello everyone and thanks for the hints. They also work as expected and I can package the provider in the web application . Nevertheless, the Configuration Reference

Re: Tomcat SSL - Issue

Priyanka, On 9/21/21 13:52, Kumawat, Priyanka wrote: Hello Team , Please find the error details as below - The site can’t provide a secure connection . xmotam01.phl.com uses an unsupported protocol ERR_SSL_VERSION or CIPHER MISMATCH Unsupported protocol – The client and server don;t

Re: Tomcat 9.0 async read becomes blocking

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

ApacheCon 2021 @Home Kicks off today 13:00 UTC

All, ApacheCon @Home starts today at 13:00 UTC (15 minutes from now, as I write this). Please join us for opening keynotes followed by the Apache Tomcat presentation track featuring the following topics: - Apache Tomcat: New and Upcoming - HTTP/2, HTTP/3, and TLS Start of the Art in our

Tomcat SSL - Issue

Hi Team , We are facing Issue while renewing SSL for the Tomcat/Apache application, the SSL was renewed and installed using the key tool . After installation when checking the https site it is giving error as given on the below screenshot - Could you please help us on this issue , is this

RE: Tomcat SSL - Issue

Attaching the screenshot again - [cid:image002.jpg@01D7AF3A.B6F2FA20] Thanks & Regards, Priyanka Kumawat | Middleware Admin T +91.7879364483 EMail - priyanka.kuma...@dxc.com DL -

RE: Tomcat SSL - Issue

Hello Team , Please find the error details as below - The site can't provide a secure connection . xmotam01.phl.com uses an unsupported protocol ERR_SSL_VERSION or CIPHER MISMATCH Unsupported protocol - The client and server don;t support a common protocol version. Thanks & Regards,

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()) {