Re: Fwd: Identifying 64k size violation for __jspService methods loaded by Tomcat

On 26/04/17 10:33, Mohammed Manna wrote: > Hello, > > Thanks for suggesting the solutions. This is closer to what I was expecting > in the original message which I sent in the past. Once again, I apologise > if I have made any Negative/Reactive comments about Apache no being > supportive enough.

Fwd: Identifying 64k size violation for __jspService methods loaded by Tomcat

-- Forwarded message -- From: Mohammed Manna Date: 25 April 2017 at 21:50 Subject: Identifying 64k size violation for __jspService methods loaded by Tomcat To: users@tomcat.apache.org Hello, I have emailed and posted a few questions over the web about this,

Re: Identifying 64k size violation for __jspService methods loaded by Tomcat

Hi, 2017-04-26 11:06 GMT+03:00 Mohammed Manna : > > -- Forwarded message -- > From: Mohammed Manna > Date: 25 April 2017 at 21:50 > Subject: Identifying 64k size violation for __jspService methods loaded by > Tomcat > To:

Re: Fwd: Identifying 64k size violation for __jspService methods loaded by Tomcat

On 26/04/17 09:06, Mohammed Manna wrote: > Hello, > > I have emailed and posted a few questions over the web about this, but > haven't received any helpful response. Since the upgrade to 8.0.39, my web > application is failing in various places since the Jasper compiler has now > got more debug

Re: Fwd: Identifying 64k size violation for __jspService methods loaded by Tomcat

Hello, Thanks for suggesting the solutions. This is closer to what I was expecting in the original message which I sent in the past. Once again, I apologise if I have made any Negative/Reactive comments about Apache no being supportive enough. I have been using various Apache libraries over the

RE: InvocationTargetException on startup after upgrade to 8.5.13

>I can't reproduce this. It may be configuration related. Please provide the >steps minimal to reproduce this from a clean 8.5.14 install. http://www.glesir.de/~frank/tomcat-startup.zip Sample CATALINA_BASE structure with a prebuilt webapp. To run it you have to adjust the contained

Problem with cookie values in 8.5.14

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, I have this code in a servlet and it's throwing an exception (below): StringBuilder sb = ...; logger.trace("cookie value: " + sb.toString()); Cookie cookie = new Cookie(cookieName, sb.toString());

Last chance: ApacheCon is just three weeks away

ApacheCon is just three weeks away, in Miami, Florida, May 15th - 18th. http://apachecon.com/ There's still time to register and attend. ApacheCon is the best place to find out about tomorrow's software, today. ApacheCon is the official convention of The Apache Software Foundation, and includes

Re: InvocationTargetException on startup after upgrade to 8.5.13

On 26/04/17 16:34, Frank Taffelt wrote: >> I can't reproduce this. It may be configuration related. Please provide the >> steps minimal to reproduce this from a clean 8.5.14 install. > > http://www.glesir.de/~frank/tomcat-startup.zip > > Sample CATALINA_BASE structure with a prebuilt webapp. To

Re: Problem with cookie values in 8.5.14

On 26/04/17 19:07, Christopher Schultz wrote: > The log message says that the value of the cookie is > "mqpp=1,kiosk=true" (without the quotes). > > The offending character (decimal 44... I was surprised it wasn't a hex > value) is a comma. I think either the Cookie class or Tomcat is >

Re: Problem with cookie values in 8.5.14

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 4/26/17 2:55 PM, Mark Thomas wrote: > On 26/04/17 19:07, Christopher Schultz wrote: > > > >> The log message says that the value of the cookie is >> "mqpp=1,kiosk=true" (without the quotes). >> >> The offending character (decimal

Re: Problem with cookie values in 8.5.14

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 4/26/17 3:18 PM, Mark Thomas wrote: > On 26/04/17 20:13, Christopher Schultz wrote: >> On 4/26/17 2:55 PM, Mark Thomas wrote: > > > >>> RFC 2109 allows quoted string to be used. In this Tomcat can >>> (and will) do what needs to be done

Re: Problem with cookie values in 8.5.14

On 4/26/2017 11:55 AM, Mark Thomas wrote: In short, yes there is a conflict. RFC 6265 does not permit ',' (and a bunch of other characters) to be used in the value and provides no escape or encoding syntax for including these characters. RFC 2109 allows quoted string to be used. In this

Re: Problem with cookie values in 8.5.14

On 26/04/17 20:13, Christopher Schultz wrote: > On 4/26/17 2:55 PM, Mark Thomas wrote: >> RFC 2109 allows quoted string to be used. In this Tomcat can (and >> will) do what needs to be done to make the cookie value 'just >> work'. > So does 6265 just basically do-away with all attempts to

Re: Problem with cookie values in 8.5.14

On 4/26/2017 12:48 PM, Mark Thomas wrote: I suggest you read the changelog for 8.5.x. Hint. Start with the entries for 8.5.0. Got it. I thought that this was a minor update. I've been running Tomcat 8.5.x for a while now so I guess I was not affected by that change. Thanks, Igal

Re: Problem with cookie values in 8.5.14

On 26/04/17 20:35, Igal @ Lucee.org wrote: > On 4/26/2017 11:55 AM, Mark Thomas wrote: >> >> >> In short, yes there is a conflict. >> >> RFC 6265 does not permit ',' (and a bunch of other characters) to be >> used in the value and provides no escape or encoding syntax for >> including these