RE: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

> From: Adhavan Mathiyalagan [mailto:adhav@gmail.com] > Subject: Re: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD What part of do not top-post do you not understand? > The Application port is configured in the catalina.properties file > HTTP_PORT=8030 > JVM_ROUTE=

Re: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

Hi, The Application port is configured in the catalina.properties file # String cache configuration. tomcat.util.buf.StringCache.byte.enabled=true #tomcat.util.buf.StringCache.char.enabled=true #tomcat.util.buf.StringCache.trainThreshold=50 #tomcat.util.buf.StringCache.cacheSize=5000

Re: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

On 11.05.2017 17:32, Adhavan Mathiyalagan wrote: Hi, 8030 is the port where the application is running. /What/ application ? Is that a stand-alone application ? For Tomcat, I cannot say (because it is not clear below what value ${HTTP_PORT} has. But from your front-end balancer, it looks

Re: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Adhavan, On 5/11/17 11:32 AM, Adhavan Mathiyalagan wrote: > 8030 is the port where the application is running. Port 8030 appears nowhere in your configuration. Not in server.xml (where you used ${HTTP_PORT}, which could plausibly be 8030) and not

Re: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Adhavan, On 5/11/17 10:57 AM, Adhavan Mathiyalagan wrote: > *Tomcat Configuration* > > HTTP/1.1 and APR > > > connectionTimeout="2" > > redirectPort="8443" maxHttpHeaderSize="8192" /> Okay, so you have a number of defaults taking

Re: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

Hi, 8030 is the port where the application is running. Regards, Adhavan.M On Thu, May 11, 2017 at 8:53 PM, André Warnier (tomcat) wrote: > On 11.05.2017 16:57, Adhavan Mathiyalagan wrote: > >> Hi Chris, >> >> *Tomcat Configuration* >> >> HTTP/1.1 and APR >> >> > >>

Re: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

On 11.05.2017 16:57, Adhavan Mathiyalagan wrote: Hi Chris, *Tomcat Configuration* HTTP/1.1 and APR ${catalina.base}/conf/web.xml *HTTPD Configuration* ServerTokens OS ServerRoot "/etc/httpd" PidFile run/httpd.pid Timeout 60 KeepAlive Off MaxKeepAliveRequests 100

Re: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

Hi Chris, *Tomcat Configuration* HTTP/1.1 and APR ${catalina.base}/conf/web.xml *HTTPD Configuration* ServerTokens OS ServerRoot "/etc/httpd" PidFile run/httpd.pid Timeout 60 KeepAlive Off MaxKeepAliveRequests 100 KeepAliveTimeout 15 StartServers256 MinSpareServers

Re: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

Hi Chris, The netstat O/P below for the CLOSE_WAIT connections tcp 509 0 :::10.61.137.49:8030:::10.61.137.47:60903 CLOSE_WAIT tcp 491 0 :::10.61.137.49:8030:::10.61.137.47:24856 CLOSE_WAIT tcp 360 0 :::10.61.137.49:8030

Re: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

Dear André, ups - yes, I confused both. FIN ;) Guido On 11.05.2017 13:37, André Warnier (tomcat) wrote: > I believe that the explanation given below by Guido is incorrect and > misleading, as it seems to confuse CLOSE_WAIT with TIME_WAIT. > See : TCP/IP State Transition Diagram (RFC793) > >

Re: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Adhavan, On 5/11/17 9:30 AM, Adhavan Mathiyalagan wrote: > The connections in the CLOSE_WAIT are owned by the Application > /Tomcat process. Okay. Can you please post your configuration on both httpd and Tomcat sides? If it's not clear from your

Re: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

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) ->

Re: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

Hi Chris, The connections in the CLOSE_WAIT are owned by the Application /Tomcat process. Regards, Adhavan.M On Thu, May 11, 2017 at 6:53 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Adhavan, > > On 5/10/17 12:32 PM,

Re: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

-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

Re: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

t backend(s). Guido -Original Message- From: Adhavan Mathiyalagan [mailto:adhav@gmail.com] Sent: Wednesday, May 10, 2017 6:32 PM To: Tomcat Users List Subject: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD Team, Tomcat version : 8.0.18 Apache HTTPD version : 2.2 There are

Re: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

ctions to the Tomcat backend(s). > > Guido > > >-Original Message- > >From: Adhavan Mathiyalagan [mailto:adhav....@gmail.com] > >Sent: Wednesday, May 10, 2017 6:32 PM > >To: Tomcat Users List > >Subject: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

RE: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

HTTP, but if you use AJP (with mod_jk) you may configure it to keep and reuse connections to the Tomcat backend(s). Guido >-Original Message- >From: Adhavan Mathiyalagan [mailto:adhav@gmail.com] >Sent: Wednesday, May 10, 2017 6:32 PM >To: Tomcat Users List >Subject: CLO

Re: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

On 10/05/17 17:32, Adhavan Mathiyalagan wrote: > Team, > > Tomcat version : 8.0.18 That is over two years old. Have you considered updating? > Apache HTTPD version : 2.2 > > > There are lot of CLOSE_WAIT connections being created at the > Application(tomcat) ,when the traffic is routed

CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

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