tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adhavan Mathiyalagan <adhav....@gmail.com>
Subject Re: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD
Date Thu, 11 May 2017 14:45:39 GMT
Hi Chris,

The netstat O/P below for the CLOSE_WAIT connections

tcp      509      0 ::ffff:10.61.137.49:8030    ::ffff:10.61.137.47:60903
CLOSE_WAIT
tcp      491      0 ::ffff:10.61.137.49:8030    ::ffff:10.61.137.47:24856
CLOSE_WAIT
tcp      360      0 ::ffff:10.61.137.49:8030    ::ffff:10.61.137.47:12328
CLOSE_WAIT
tcp      511      0 ::ffff:10.61.137.49:8030    ::ffff:10.61.137.47:24710
CLOSE_WAIT
tcp      479      0 ::ffff:10.61.137.49:8030    ::ffff:10.61.137.47:33175
CLOSE_WAIT
tcp      361      0 ::ffff:10.61.137.49:8030    ::ffff:10.61.137.47:58084
CLOSE_WAIT
tcp      531      0 ::ffff:10.61.137.49:8030    ::ffff:10.61.137.47:42030
CLOSE_WAIT
tcp      971      0 ::ffff:10.61.137.49:8030    ::ffff:10.61.137.47:17692
CLOSE_WAIT
tcp      361      0 ::ffff:10.61.137.49:8030    ::ffff:10.61.137.47:60303
CLOSE_WAIT


10.61.137.49 -> Application IP
10.61.137.47 -> Load balancer IP

Regards,
Adhavan.M

On Thu, May 11, 2017 at 7:06 PM, André Warnier (tomcat) <aw@ice-sa.com>
wrote:

> On 11.05.2017 15:30, Adhavan Mathiyalagan wrote:
>
>> Hi Chris,
>>
>> The connections in the CLOSE_WAIT are owned by the Application /Tomcat
>> process.
>>
>
> Can you provide an example output of the "netstat" command that shows such
> connections ? (not all, just some)
> (copy and paste it right here)
> ->
>
>
>
>> Regards,
>> Adhavan.M
>>
>> On Thu, May 11, 2017 at 6:53 PM, Christopher Schultz <
>> chris@christopherschultz.net> wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA256
>>>
>>> Adhavan,
>>>
>>> On 5/10/17 12:32 PM, Adhavan Mathiyalagan wrote:
>>>
>>>> Team,
>>>>
>>>> Tomcat version : 8.0.18
>>>>
>>>> Apache HTTPD version : 2.2
>>>>
>>>>
>>>> There are lot of CLOSE_WAIT connections being created at the
>>>> Application(tomcat)  ,when the traffic is routed through the Apache
>>>>   HTTPD load balancer to the Application running over tomcat
>>>> container. This leads to slowness of the port where the
>>>> Application is running and eventually the application is not
>>>> accessible through that particular PORT.
>>>>
>>>
>>> Please clarify: are the connections in the CLOSE_WAIT state owned by the
>>> httpd process or the Tomcat process?
>>>
>>> In case of the traffic directly reaching the Application PORT
>>>> without HTTPD (Load balancer) there is no CLOSE_WAIT connections
>>>> created and application can handle the load seamlessly.
>>>>
>>>
>>> - -chris
>>> -----BEGIN PGP SIGNATURE-----
>>> Comment: GPGTools - http://gpgtools.org
>>> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>>>
>>> iQIyBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlkUZcoACgkQHPApP6U8
>>> pFgiuA/4uARxnF+2c6E+oAIUVX+j2vb+RBicYKAuO6KW67cXtP5UBBFmR5jlLOyr
>>> uz6M8qDB0H89IkEgny3oQeaZYVvDeFokthAwTe3SCrtfsWb0d39EHGUoNfxZQnCZ
>>> hjygWvxmmuO84RqNrO0Q1+UNWYlPB0cK3SLFZRmh59zJg+C8FBDG2OAIEpevXw0O
>>> yPdnSHq6KwX3kZA3KZWx03YUBwjjTk1TLvfq8vfmMmp96THd4QXqvhI46xOcV/sp
>>> KBUrRIQhjTDPsm7EH268ffve0kgcXIkmh7qj2cCl07+CrVn6TbPXSwQEm5j5CjIF
>>> toMywVs9szCwT0qRlOaLALQyXdUJnuUwBNjTp+DIPIukeUZ1BqwC/DopTHftzr6u
>>> oT7ZWurZBFCZUSCsbfyi6c7FTRs/jqT3eIo2he5Q3AxtZ2CayzC4xgx2vxqrBTkV
>>> OEESNhnzH3QdJTFnDDQCLtrr7lHyZ6/4MKDUK9Ax2LjVt63kRdIW31VWs0Y2KqbW
>>> OGd9apwNe9FrTEGn7zAw+lXKKmWr/2DMEViawmKUxtoZMQsrW6NPTvlNmKX4zgYM
>>> eU0ZHE5d1SMYwfPXzH+w/Cqv+hZMssNfKMZ9rdjPd+rf8xgzL27tvMvg/rjvrRfF
>>> kuiNtfFcA34CDfR+bEed2eYAAUMizb+uzPUHhVAZMaR8T8CXGQ==
>>> =nMBw
>>> -----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
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message