You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Louis Zipes <Lo...@kdrp.com> on 2019/04/11 20:42:35 UTC
maxActive and maxWaitMillis set to "-1" in Tomcat 8.5
Hi all,
I'm upgrading from 7.0.54 to 8.5 and I know that MaxActive and maxWaitMillis replace MaxActive and MaxWait respectively but my third party vendor provided the old parameters as set to '-1' when they packaged the application with 7.0.54.
My questions is what does '-1' mean for MaxActive and maxWaitMillis parameters? Is it infinite? Is it dangerous to continue to use those values or should I do something like 200/10,000 respectively?
Thanks, Louis
---------------------------------------
CONFIDENTIALITY NOTICE: This message is for intended addressee(s) only and may contain information that is confidential, proprietary or exempt from disclosure. If you are not the intended recipient, please contact the sender immediately. Unauthorized use or distribution is prohibited and may be unlawful.
RE: maxActive and maxWaitMillis set to "-1" in Tomcat 8.5
Posted by Louis Zipes <Lo...@kdrp.com>.
*maxTotal replaces maxActive in Tomcat 8.5
-----Original Message-----
From: Louis Zipes [mailto:Louis.Zipes@kdrp.com]
Sent: Thursday, April 11, 2019 4:43 PM
To: Tomcat Users List
Subject: maxActive and maxWaitMillis set to "-1" in Tomcat 8.5
Hi all,
I'm upgrading from 7.0.54 to 8.5 and I know that MaxActive and maxWaitMillis replace MaxActive and MaxWait respectively but my third party vendor provided the old parameters as set to '-1' when they packaged the application with 7.0.54.
My questions is what does '-1' mean for MaxActive and maxWaitMillis parameters? Is it infinite? Is it dangerous to continue to use those values or should I do something like 200/10,000 respectively?
Thanks, Louis
---------------------------------------
CONFIDENTIALITY NOTICE: This message is for intended addressee(s) only and may contain information that is confidential, proprietary or exempt from disclosure. If you are not the intended recipient, please contact the sender immediately. Unauthorized use or distribution is prohibited and may be unlawful.
B�KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB�� [��X��ܚX�KK[XZ[
� \�\��][��X��ܚX�P �X�]
�\X�K�ܙ�B��܈Y][ۘ[��[X[� �K[XZ[
� \�\��Z[ �X�]
�\X�K�ܙ�B�
---------------------------------------
CONFIDENTIALITY NOTICE: This message is for intended addressee(s) only and may contain information that is confidential, proprietary or exempt from disclosure. If you are not the intended recipient, please contact the sender immediately. Unauthorized use or distribution is prohibited and may be unlawful.
Re: maxActive and maxWaitMillis set to "-1" in Tomcat 8.5
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Louis,
On 4/11/19 16:42, Louis Zipes wrote:
> I'm upgrading from 7.0.54 to 8.5 and I know that MaxActive
maxTotal
> and maxWaitMillis replace MaxActive and MaxWait respectively but my
> third party vendor provided the old parameters as set to '-1'
> when they packaged the application with 7.0.54.> My questions is
> what does '-1' mean for MaxActive and maxWaitMillis parameters?
> Is it infinite? Is it dangerous to continue to use those values or
> should I do something like 200/10,000 respectively?
The complete documentation is available here:
https://commons.apache.org/proper/commons-dbcp/configuration.html
maxTotal = -1 means "no limit"
maxWaitMillis = -1 means "wait forever"
IMHO, maxTotal = infinite is completely insane. Even if the limit is
huge (like 1000), there should definitely be a limit on the
connection-pool size.
Also, for me, maxWaitMillis = infinite is insane. If a connection
isn't available after some reasonable amount of time, waiting longer
isn't going to help. It probably means that something is terribly
wrong with your service. You WANT these attempts to fail instead of
holding-up a request-processing thread which will bring-down your web
application.
For development, I'd set maxTotal=1 to make sure you don't have any
connection leaks. For production, it's up to you. We run a service
which typically has 200-300 logged-in users per Tomcat node and we
have a modest maxTotal="10" and maxWait="10000" on each node.
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlyvq14ACgkQHPApP6U8
pFhs+A//YX4nTAEXNXnHnId+PzF+MMu2+TxGMPqlMThAu1xV18YEF5tymc634E3A
yTL5A60+Q7rTIElDCSY9eRnjPwHNPg4fYULcHPJEdsmlsZXO2bq3i2xwa7sNIvOG
I1CaaaFugXADGkvWCwVEMOYk4E4PaN67YMvDz7jBuqgipBo3yPMojxYKLCH6oG3K
4AIGkygQhpMFAbQJw0sdwBHw+8sMGep5wZjb1BdEiaksM8KcF7rkdtJqEvCl3VGH
0YL52GEsSgzKpJs8onssFaN/RYCFJ+o+UEcCOxQ1Fy3X9T/kxu1j8eyuXzVLnNCI
wfXE0NtoUwTQ1jFU96vPOG0jE4QW/fQPxMuVwL8StSz0Prm8BiAcrS3I2kvjb0DU
h3VIHb35p4a8yssMvW3s5n/wFyliLBA9U96pIrnIvsQ02ReCIbKs/7/sMUdZu9ea
oGN59R8cnrsC0E9Y1WbChdS+7i95QxPp0zox/jl6A7OAvODCrtnvXti+x5RW4Bg5
ayPT2vgcakY+RU2s7Yb+3ukNGU/uspC7NAJgJ8jtMbYP08uFuWDE9dupa8BuAjU5
xRgE8YJWfULmeVojtqUkX36t3Q6A9SaGw6J8BxlPiyWD/WQXv32dv0Hx6+INVNea
ICKfWOENe5VGB7J7kixhBVgZCNuSxYOxwh0Q9Xsujeoz9KHBFls=
=ybtQ
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org