JSP compilation 65535 bytes limit

Hello Team, Recently we did a upgrade existing tomcat from 7.0.42 to 7.0.76 on windows box. Post the up gradation we are seeing following error in couple of JSPs org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: [231] in the generated java file:

RE: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

Dear Adhavan, I think this is quiet normal, because the browser clients "in front" will reuse connections (using keep-alive at TCP level) but an in-between load balancer may be not work or configured in this way and will use a new connection for each request to the backend. Then, you'll see a

Re: trimSpaces removing whitespace from html

Thanks for the quick reply. This is the code that i added to the web.xml file to activate trimSpaces: trimSpaces true This is the HTML code: 1. Before class="mrf-article mrf-article--photo mrf-page mrf-noFillet mrf-author mrf-m mrf-image "> 1.After

[ANN] Apache Tomcat 9.0.0.M21 available

The Apache Tomcat team announces the immediate availability of Apache Tomcat 9.0.0.M21. Apache Tomcat 9 is an open source software implementation of the Java Servlet, JavaServer Pages, Java Unified Expression Language, Java WebSocket and JASPIC technologies. Apache Tomcat 9.0.0.M21 is a

Re: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

Thanks Guido ! On Thu, May 11, 2017 at 12:02 PM, Jäkel, Guido wrote: > Dear Adhavan, > > I think this is quiet normal, because the browser clients "in front" will > reuse connections (using keep-alive at TCP level) but an in-between load > balancer may be not work or configured

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

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: trimSpaces removing whitespace from html

Yes, the problem happens in the class attribute string. They are some examples but it happened throughout the files in many cases. I am using .jsp files Also, in the second example that i gave, you can see that mrf-video was removed as well as mrf-m and mrf-image being joined. This was the

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

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

-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

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

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

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: Security question

2017-05-11 17:21 GMT+03:00 Pesonen, Harri : > > Hello, > > the following lists Tomcat versions 8.5.0 – 8.5.12, does it mean that the problem has been fixed in 8.5.13 and later? yes http://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.13 Regards, Violeta > >

Security question

Hello, the following lists Tomcat versions 8.5.0 - 8.5.12, does it mean that the problem has been fixed in 8.5.13 and later? https://nvd.nist.gov/vuln/detail/CVE-2017-5651 I assume that it has been fixed, as 8.5.13 readme has: * [Fix:]

Re: CLOSE_WAIT between Application (Tomcat) and Apache HTTPD

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) CLOSE-WAIT represents waiting for a connection termination request from the local user. TIME-WAIT represents

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: trimSpaces removing whitespace from html

Am Donnerstag, den 11.05.2017, 09:23 -0400 schrieb Christopher Schultz: > So, removing the trailing space in the "class" attribute's value? That too - but have a look at: mrf-mmrf-image it was before / should be: mrf-m mrf-image there are missing whitespaces in the actual class attributes

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

-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: trimSpaces removing whitespace from html

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 David, On 5/11/17 3:27 AM, David Kavanagh wrote: > Thanks for the quick reply. > > This is the code that i added to the web.xml file to activate trimSpaces: > > trimSpaces > true > > This is the HTML code: > > 1. Before > >

Re: Embedded tomcat does not find web-fragment in jars outside web-inf\lib

Am 10.05.2017 um 19:59 schrieb Mark Thomas: On 10/05/17 12:40, Michael Heinen wrote: Am 10.05.2017 um 12:18 schrieb Mark Thomas: On 10/05/17 10:26, Michael Heinen wrote: Am 10.05.2017 um 00:40 schrieb Mark Thomas: On 09/05/17 15:25, Michael Heinen wrote: Hi all, I am currently mirgating an

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: trimSpaces removing whitespace from html

On 11 May 2017 15:34:32 BST, David Kavanagh wrote: >Yes, the problem happens in the class attribute string. >They are some examples but it happened throughout the files in many >cases. > >I am using .jsp files > >Also, in the second example that i gave, you can see

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

> 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=dl360x3805.8030