On 10/31/16 12:54 PM, Mark Thomas wrote:
On 31/10/2016 19:52, Rallavagu wrote:
As per https://tomcat.apache.org/tomcat-7.0-doc/config/executor.html it
appears "maxIdleTime" could be what I am looking for. Is there a
corresponding config parameter for internal thread pool?
Which part of "hard
On 31/10/2016 19:52, Rallavagu wrote:
> As per https://tomcat.apache.org/tomcat-7.0-doc/config/executor.html it
> appears "maxIdleTime" could be what I am looking for. Is there a
> corresponding config parameter for internal thread pool?
Which part of "hard-coded" wasn't clear?
Mark
>
> On 10/
As per https://tomcat.apache.org/tomcat-7.0-doc/config/executor.html it
appears "maxIdleTime" could be what I am looking for. Is there a
corresponding config parameter for internal thread pool?
On 10/31/16 12:44 PM, Mark Thomas wrote:
On 31/10/2016 19:38, Rallavagu wrote:
Here is the configur
On 10/31/16 12:44 PM, Mark Thomas wrote:
On 31/10/2016 19:38, Rallavagu wrote:
Here is the configuration snippet.
As you can see, _not_ using executor. Thanks.
When using the internal thread pool, that delay is hard-coded to 60s. If
you want to configure it, use an Execut
On 31/10/2016 19:38, Rallavagu wrote:
> Here is the configuration snippet.
>
>
>
>
> maxThreads="500"
>connectionTimeout="2"
>redirectPort="28443" />
>
>
>
> As you can see, _not_ using executor. Thanks.
When using the internal
Here is the configuration snippet.
As you can see, _not_ using executor. Thanks.
On 10/31/16 11:58 AM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rallavagu,
On 10/31/16 1:59 PM, Rallavagu wrote:
All,
Tomcat 7.0.70 with bio connector
I hav
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rallavagu,
On 10/31/16 1:59 PM, Rallavagu wrote:
> All,
>
> Tomcat 7.0.70 with bio connector
>
> I have been monitoring JMX for "currentThreadCount" and
> "currentThreadsBusy". If I understand correctly,
> currentThreadCount would not exceed "max
All,
Tomcat 7.0.70 with bio connector
I have been monitoring JMX for "currentThreadCount" and
"currentThreadsBusy". If I understand correctly, currentThreadCount
would not exceed "maxThreads" configuration and "currentThreadsBusy"
apparently shows "busy" threads at that time. I am wondering i
I am studying the following diagram:
https://tomcat.apache.org/tomcat-9.0-doc/architecture/
requestProcess/request-process.png
And I have the following question: is StandardWrapperValve in charge of
creating new instances of servlets?
If I wanted to intercept servlet instance(s) prior to service
