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 On Tue, Jun 9, 2015 at 9:14 AM, Christopher Schultz < ch...@christopherschultz.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > 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_Requ > 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 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > Comment: GPGTools - http://gpgtools.org > > iQIcBAEBCAAGBQJVdxD4AAoJEBzwKT+lPKRYc6sP/RDSV9IeARJXJIo4f6VeRwJv > S/RcHDq8tmUmT1Z/gvX6nzTeEiHclIXoXMY3AJ0wg0LJHHQHMw+Z5waX1j76/hoQ > TDmO/qNewqyWnI3oCsg6h7yrjtugs9hsqK77LJCUY0954qrSP/+McKUNQTLW3sGP > Ik7ImDNaFHGZZvwgaq1DAzL9Sa+QM2XiTZqnM5yxykW2tmy1kOv4/47Pb97NUJyz > 2C2WjZqgQBIRVOh7L5Wg8tp9SLtZ548oUSJopadoLaqsdvlva8H9v7Lz/ESOS8V8 > 3voPz9owNDn+5E641piv9ykHh86emltFE1uVRaV3ryX1LW11mGi0Qhqhn9DC2U2b > WeR5VZ0iiSiS/BdnNN+8hnT1o32GquLkJPx4aGco3kjeLV2ADBpTNaAupwYfRl9Y > NVbM9CZlLR97CPic4qmV1yECgv1UDaSp4sRE5G6SFc1UnxPDUIi2EVAPYthKF66Z > mtVHBOgwWARGohqlbtjuIugPAOu3RYnV4qg7ZqWfxPrnvXTWjGOETOzeidEdn9hb > EcXYcTRTShk609vWXA5BvPK/H8eJ3Mg84a0wRex8NdlsuZZaQFd/WfVXvklk5ndl > ge0siyVLSynHXdjDCnPm5sKyHREyCOUjgYtOQky0b7sHS36i2CPdKH0srQ9DngkY > +crYqQ+kzEH61VTadc1r > =JPLZ > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
