Christopher,
Il 19/01/2022 20:32, Christopher Schultz ha scritto:
Ivano,
On 1/19/22 10:58, Ivano Luberti wrote:
Mark, Christopher
Il 19/01/2022 15:31, Christopher Schultz ha scritto:
Mark,
On 1/19/22 05:00, Mark Thomas wrote:
On 18/01/2022 23:16, Christopher Schultz wrote:
All,
There
On a Tomcat 9.x dedicated Linux server with 16G of memory, how much memory
would you allocate for the OS?
Assume there is no file processing taking place. Also assume Tomcat is
communicating primarily with a PostgreSQL database and Apache web server each
running on their own dedicated
Ivano,
On 1/19/22 10:58, Ivano Luberti wrote:
Mark, Christopher
Il 19/01/2022 15:31, Christopher Schultz ha scritto:
Mark,
On 1/19/22 05:00, Mark Thomas wrote:
On 18/01/2022 23:16, Christopher Schultz wrote:
All,
There are a bunch of parameters in SSLHostConfig which are
documented[1]
Mark, Christopher
Il 19/01/2022 15:31, Christopher Schultz ha scritto:
Mark,
On 1/19/22 05:00, Mark Thomas wrote:
On 18/01/2022 23:16, Christopher Schultz wrote:
All,
There are a bunch of parameters in SSLHostConfig which are
documented[1] to be "OpenSSL Only" and "JSSE only". I thought
Mark,
On 1/19/22 05:00, Mark Thomas wrote:
On 18/01/2022 23:16, Christopher Schultz wrote:
All,
There are a bunch of parameters in SSLHostConfig which are
documented[1] to be "OpenSSL Only" and "JSSE only". I thought we made
it so either configuration could be used with either underlying
Mark,
On 1/14/22 11:27, Mark Thomas wrote:
On 14/01/2022 14:50, Christopher Schultz wrote:
But I'm not sure how to get the "[Service]" name. I can cast
HTtpServletRequest to o.a.c.connector.Request and from there I can get
the o.a.coyote.Request but neither of those seem to have access to
On 18/01/2022 23:16, Christopher Schultz wrote:
All,
There are a bunch of parameters in SSLHostConfig which are documented[1]
to be "OpenSSL Only" and "JSSE only". I thought we made it so either
configuration could be used with either underlying crypto engine. Is
that not true? Or is it only
On 19/01/2022 09:37, Levent KAYA wrote:
Hi All,
Is there "Surge protection mode" feature on data source definition on
Tomcat ?
No.
I'm not convinced it is necessary. A well configured database connection
pool should handle spikes in demand.
Mark
Surge protection is designed to prevent
Hi All,
Is there "Surge protection mode" feature on data source definition on
Tomcat ?
Surge protection is designed to prevent overloading of a data source when
too many connections are created at the same time.
*Connection pool advanced settings*
