calder wrote:
We've never had occasion to use the password, because we disable shutdown
(the better option).
Never did understand this Tomcat oddity. What other application is
configured by default to open a tcp socket just to receive a shutdown
command? Then there the default password, both
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Calder,
On 5/9/20 00:36, calder wrote:
> On Fri, May 8, 2020 at 9:07 PM calder
> wrote:
>>
>> On Fri, May 8, 2020, 19:20 Robert Hicks
>> wrote:
>>>
>>> I am trying to find what the password complexity can be. I've
>>> looked at several hardening
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Daniel,
On 5/9/20 12:34, daniel@dell.com wrote:
> We want to use APR to call openssl also do with native to support
FIPS mode in tomcat.
>
> Software info Tomcat/9.0.34 libtcnative-1-0-1.2.23-15.30.x86_64
Where did you get that? Is it
On Sat, 9 May 2020 at 9:09 PM, Vikas Kumar wrote:
> I did not know about the images being dropped.
>
> Here are the steps I depicted in the image:
>
> Step 0: Request accepted by OS
> Step 1: Request sent to Tomcat. Tomcat accepts the request if it's internal
> queue is not full, else rejects
On 09/05/2020 14:08, Vikas Kumar wrote:
> I did not know about the images being dropped.
>
> Here are the steps I depicted in the image:
>
> Step 0: Request accepted by OS
> Step 1: Request sent to Tomcat. Tomcat accepts the request if it's internal
> queue is not full, else rejects the request
As per my understanding (using a Spring Boot app with Tomcat server), we
define:
- Max no. of worker threads (maxThreads, default 200)
- Tomcat queue size (maxConnections, default 8192 for APR, 1 for
NIO). When all worker threads are busy, requests are placed into the queue.
As
On Sat, May 9, 2020, 07:16 Vikas Kumar wrote:
> As per my understanding (using a Spring Boot app with Tomcat server), we
> define:
>
>- Max no. of worker threads (maxThreads, default 200)
>- Tomcat queue size (maxConnections, default 8192 for APR, 1 for
>NIO). When all worker
We want to use APR to call openssl also do with native to support FIPS mode in
tomcat.
Software info
Tomcat/9.0.34
libtcnative-1-0-1.2.23-15.30.x86_64
configuration as below:
When enable debug info in tomcat will see
09-May-2020 00:51:35.358 FINE [https-openssl-apr-8443-exec-1]
Hi Mark,
Thanks for the detailed reply. I think I get it now.
The problem I was trying to solve was to dynamically control the
concurrency/in-flight requests (requests being processed by worker threads
+ requests in queue) based on the response times of requests (time spent in
queue + time spent
I did not know about the images being dropped.
Here are the steps I depicted in the image:
Step 0: Request accepted by OS
Step 1: Request sent to Tomcat. Tomcat accepts the request if it's internal
queue is not full, else rejects the request
Step 2: Tomcat adds the request to the queue if all
10 matches
Mail list logo
