tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David kerber <dcker...@verizon.net>
Subject Re: Increasing incoming connection request in a queue
Date Tue, 05 Aug 2014 13:00:57 GMT
On 8/5/2014 8:49 AM, Dhaval Jaiswal wrote:
> After reviewing your comments found that in below tags i have not defined
> the maxThreads limit in Connector Port 8080. While the same exists with the
> connector port 8009. Default limit of maxThreads is 200.
>
> LB is communicating with tomcat on port 8080. I think by increasing
> maxThreads limit will help me. What is your take. Is it going to create any
> performance issue If i will increase maxThreads to 10000 in connector 8080.

That depends on your hardware.  Too many threads with not enough CPU 
and/or RAM to handle may make things worse.


>
>
> <Connector port="8080" protocol="HTTP/1.1"
>                 connectionTimeout="20000"
>                 redirectPort="8443" />
>
>
> <Connector port="8009" protocol="AJP/1.3"
>                 connectionTimeout="20000"
>                 redirectPort="8443" maxThreads="10000"/>
>
>
>
>
> On Tue, Aug 5, 2014 at 2:23 AM, Christopher Schultz <
> chris@christopherschultz.net> wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> Dhaval,
>>
>> On 8/4/14, 1:56 PM, Dhaval Jaiswal wrote:
>>> <Connector port="8080" protocol="HTTP/1.1"
>>> connectionTimeout="20000" redirectPort="8443" />
>>
>> You need to check the Tomcat configuration guide for the default
>> settings that you are getting. It is also pretty clear which
>> configuration attributes affect the maximum number of total and
>> simultaneous connections, etc.
>>
>>>
>>
>>
>>>
>>>>> if you really have a problem now, or if you are just
>>>>> speculating without
>>> real facts. If you have a real problem, what is it ? is your Tomcat
>>> really refusing browser connections ? if yes, does this happen all
>>> the time, or only at specific times ?
>>>
>>>
>>> It happens only at specific time. While trying to hit some api and
>>> response did not received in time. For such request I have kept the
>>> time out of 100 seconds (that is the requirement). As the first
>>> request/thread itself is in waiting mode new incoming
>>> request/thread will be very slow and after some time logout issue
>>> will occur or it will slow down the performance for other requests
>>> and resultant site will be loading very slow. Moreover, it will
>>> start throwing below errors. Henceforth, decided to increase
>>> incoming connection request. I am not sure whether acceptQueue or
>>> some another parameter need to add.
>>>
>>> Caused by: java.net.SocketTimeoutException: connect timed out at
>>> java.net.PlainSocketImpl.socketConnect(Native Method) at
>>> java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at
>>> java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>>>
>>>
>> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>>> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at
>>> java.net.Socket.connect(Socket.java:519) at
>>> sun.reflect.GeneratedMethodAccessor93.invoke(Unknown Source) at
>>>
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>
>>>
>> at java.lang.reflect.Method.invoke(Method.java:597)
>>
>> This is not enough information: you need to post the whole stack trace.
>>
>>>>> The browser clients trying to get a connection to Tomcat, or
>>>>> the
>>> postgres database which you seem to be using for authentication ?
>>>
>>> We have three tier architect. It will first try to get the
>>> connection from web server (haporxy) to tomcat and then to
>>> database.
>>
>> Confusing.
>>
>> - -chris
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1
>> Comment: GPGTools - http://gpgtools.org
>> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>>
>> iQIcBAEBCAAGBQJT3/LSAAoJEBzwKT+lPKRYy8oP/jnUbF4db7rHr3E5Ceehl791
>> +frtDPcfqsXe5LOyBAE0MJ/qCrjEMAFtun78ofCQnwh/Tx20hr9PAIk9MAzcOlQe
>> jgCdwTGRTZa74McNn6xpt7gfHJLlgMDngt39Rzl7CmcvZ2V3ruwT8IC2rInRo9mM
>> fnr2jMdMuOuzcAZTMJPm4xZhN5WEzzZFP9o0Dmwn+XC9e27ufKYg6mgPrTISyO6A
>> 0g/MKXJKjKRM7fOd/Q+rW0SjRZUMLOekacBNbM0JHvRh+PmHDfeRmVwlqgZ9RpcC
>> yax2J1bbf7tprLUG+tKOBEn5JoIbV10rfhNBufnRFYR2Jde4+d1Df/IWTTglzFAj
>> F1wWDwKgSkIMk0HF5u/pF8BtiMQ8V4jmwFBEFoRS78iB+ynpdYU0Awj6ZcAB/Lnv
>> BgrRnsYp/kWjr7ycsk1BvdKZJ1gp+lLuhVU0J2nab4jj37kfJjGwW5WWGbR3WTG9
>> PLi+FAOOonMiGzx6FYRAum6rzCFeJll6CUE1PMFp70DQEM9WMYFDMZJEmo7BWjw0
>> 7kNMxhopKqtsvhBO2aVtU4B2ZaV35Sucn9KNlgYa8Y1BlKx2RrvClNLk0XYObh1j
>> 0/4JKIGjSAFNVHqsxWz/oy1+lD4sZAJ6mmii7Fud71W5n6tV88OWWxwtSRxuvtTi
>> XJhlk43/9rqfr2yLWgE/
>> =E3+3
>> -----END PGP SIGNATURE-----
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message