-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Ravi,
On 6/9/15 1:48 PM, Ravi Kiran wrote: > Few things we tried: - Changed mod_jk to mod_proxy where requests > are passed to tomcat as http:8080 instead of AJP but we still get > the same issue intermittently. - Enabled failed request filter and > it doesn't report anything nor stop the requests stating bad > requests > > unfortunately, running out of options Have you checked to make sure that the request parameters aren't illegally-formatted as Konstantin suggested might be the case? It might help if you provided an example packet capture of a request whose parameters have been ignored. Also, are you testing against Tomcat 7.0.latest, or still 7.0.54? - -chris > On Tue, Jun 9, 2015 at 9:14 AM, Christopher Schultz < > ch...@christopherschultz.net> wrote: > > Konstantin, > > On 6/9/15 5:04 AM, Konstantin Kolinko wrote: >>>> 2015-06-04 18:40 GMT+03:00 Ravi Kiran >>>> <ravikiran...@gmail.com>: >>>>> Hi, >>>>> >>>>> I am writing to get some pointers on a strange issue which >>>>> are facing in tomcat in one of our client environments. >>>>> >>>>> Setup: 4 Webservers connecting to 2 tomcat using mod_jk >>>>> (load balanced) >>>>> >>>>> Issue: Request parameters GET/POST are coming as null to >>>>> the application intermittently i.e, filter in web app dumps >>>>> the request parameters and finds everything empty. TCP >>>>> dumps are inspected and packets are reaching tomcat even >>>>> during the failure cases. Parameters are available in >>>>> tcpdump but lost in between before it reaches application. >>>>> This happens only on one specific client environment which >>>>> makes it even difficult to isolate the problem. >>>>> >>>>> Tomcat Version: 7.0.54 >>>>> >>>>> Please suggest some pointers to debug and resolve this >>>>> issue. I can provide more info if needed. >>>>> >>>> >>>> >>>> The Servlet API has no way to report errors (such as >>>> IOException) from request.getParameter() family of methods. >>>> There is a Tomcat-specific request attribute that is set to a >>>> non-null value when parsing of parameters fails. >>>> >>>> See org.apache.catalina.filters.FailedRequestFilter [1] as a >>>> sample of code. >>>> >>>> [1] >>>> http://tomcat.apache.org/tomcat-7.0-doc/config/filter.html#Failed_R equ > >>>> est_Filter > > +1 > > I >>>> > re-read the OP and I was under the impression that the Filter was > reading the request parameters properly, but that the servlet was > then re-reading the parameters and getting nulls. > > Having re-read that, I suspect Konstantin's analysis is correct, > and that the parameter values were probably broken in some way. > > -chris >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVdyqEAAoJEBzwKT+lPKRYsYgP/0wtTEUpiod6rCofO5xAxomT gye06hD+0DUNB4L9LwIxni+KSiW/0T85eMkKmD01SSY3wHYVlY792jkptFgB65DA +UNATRZoiRgclWB1kIXW6IpeAfltFSfDyizj2UrEHX885xuBm4NZ4L4laBuY4aYN QXmnMmLZQwXw352+GaLB/o8Wwy5l2ehsN80udIHIazbtGiL+KkRYLVAbrrrD0pbW bt77BShW2spyVog6hGRDC0zDEwD18A7PIMu1ANk1MZC3QJbTUFrHPvVyp/1zz8JK sgte5pstRawDOVoh135oIVLDs77wCcC+i6LOBils0g65sPEOHTFTkC8E7eALabX4 seIG+UDdLS84S/ZewMUZP2TSBBthMmrxMBsEt5rtlcsy00/VO+0IBct8m0cO20vq hLEHxm/hFw72ogzs0a65P0HsRt8ay/tBnzE3ERQ3n1iljyWSqWbyFzH27voyWLbm BhifTML7hVZjDsLK9QScsHCrMYnTJuL/6p1bxeVf5CsdnixC8/u6zpxMlkvjhmW6 NKX+3Jopmjvq7lOSnR6JqZWVHqh3pi1XvLoIHroLOpYT9dQDUtKOqjv0Og6Qt3zv B08u6y5Q2xlFMtev2vscTKTnObdk6b3e21DHl3x66NP/1iDk6Zl8joE1HuSztNm+ 37H0DeidwcwHkf2QdzdZ =Kxwn -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
