What is maxConnections attribute in Tomcat and what is the optimum value in
Unix machine?
Thanks,
Raj
--
Thanks&Regards Rajendra
On 10/01/2019 19:55, Mark Thomas wrote:
> I've just tracked down one leak although it is a relatively small one.
> Next steps are to fix that leak and then find the next one. And then repeat.
Found it.
The leak impacted NIO and NIO2 when used with OpenSSL.
The bug is in Tomcat Native. I have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 1/11/19 12:23, Mark Thomas wrote:
> On 10/01/2019 19:55, Mark Thomas wrote:
>
>
>
>> I've just tracked down one leak although it is a relatively small
>> one. Next steps are to fix that leak and then find the next one.
>> And then repeat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rajendra,
On 1/11/19 10:20, Rajendra Popuri wrote:
> What is maxConnections attribute in Tomcat
It is all but deprecated IMHO.
http://tomcat.apache.org/tomcat-9.0-doc/config/http.html#Standard_Implem
entation
Search for "maxConnections".
Then re
Hi Chris,
Thanks for prom response.
Actually I am trying to understand the attributes acceptCount vs
maxConnections. Assuming this is the maximum socket connections tomcat can
handle In a time and this can be restricted with ulimit -f in linux.
Please advise.
Thanks,
Rajendra
On Fri, Jan 11,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rajendra,
On 1/11/19 12:52, Rajendra Popuri wrote:
> Actually I am trying to understand the attributes acceptCount vs
> maxConnections.
They are both limits, but are implemented in different places.
The "acceptCount" is implemented in the TCP/IP
On 11/01/2019 17:31, Christopher Schultz wrote:
> Mark,
>
> On 1/11/19 12:23, Mark Thomas wrote:
>> On 10/01/2019 19:55, Mark Thomas wrote:
>
>>
>
>>> I've just tracked down one leak although it is a relatively small
>>> one. Next steps are to fix that leak and then find the next one.
>>> And t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mark,
On 1/11/19 13:50, Mark Thomas wrote:
> On 11/01/2019 17:31, Christopher Schultz wrote:
>> Mark,
>>
>> On 1/11/19 12:23, Mark Thomas wrote:
>>> On 10/01/2019 19:55, Mark Thomas wrote:
>>
>>>
>>
I've just tracked down one leak although
On 11/01/2019 21:07, Christopher Schultz wrote:
> Mark,
>
> On 1/11/19 13:50, Mark Thomas wrote:
>> On 11/01/2019 17:31, Christopher Schultz wrote:
>>> Mark,
>>>
>>> On 1/11/19 12:23, Mark Thomas wrote:
On 10/01/2019 19:55, Mark Thomas wrote:
>>>
>>>
> I've just tracked down one lea
