Re: Fwd: Apache Tomcat 7 -Parameters lost
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Kartheek, On 6/12/15 12:32 PM, kartheek desineedi wrote: We are facing a weird issue where a similar configuration is yielding unexpected results for consecutive requests on Tomcat 7.0.54. We have enabled the request dumper filter on Tomcat 7 and it shows that consecutive requests are missing the parameters. What do you mean consecutive requests? Due to this our application is throwing a backend error and giving a bad user experience of not letting the user complete a transaction. Did anyone face a similar issue on Tomcat 7 ?I can share more configuration files as required to help give more details on the issue. Did you follow-up on all the questions we've already asked, and the ideas we've presented? You have a handful of replies on your earlier thread. Helpful pointers are greatly appreciated. LOG link: http://www.filedropper.com/requestdumper TCP dump -8009 http://www.filedropper.com/tcpdump I looked, and these don't tell me anything. I have no idea what I'm looking at. Additional Info: We are not aware of any specific pattern.The transaction is going through Browser [HTTP | Port 80] Web Server [HTTP | Port 80] Mod JK [AJP 13 | Port 8009] Tomcat [AJP 13 | Port 8009].The parameters are submitted through a form POST.We roughly see this issue once in 5 times.The log which we shared is from the tomcat's request dumper filter which is supposedly the first filter before any of the application level filters are invoked which means that our application is not even receiving them.Hope this gives you a better idea. So, is the RequestDumperFilter seeing the parameters but your application is not? Or are you saying that not even the RequestDumperFilter is seeing the parameters? Added the tcp dump for port 8009 which is the last layer before the request dumper log and the parameters are found in both the cases.(please ignore the file name in the logs) - -chris -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVezQCAAoJEBzwKT+lPKRYZf8QAKsRxMbOHgEsyJIvX6hEgqvY SMnVGSdTaIuwcxUqyvsqzTGdjO2yG3dwZO8otd/IHHOLBVko5s/irAAnYVS0o517 OJFRI0XG1mtaHwVy3Z9xgCvxgL7pSLbLoVBA+5t+zJR28RM3hhc8pRGNB/mZ5gYS FBQGFFJkIwdIN4RZNa4Z38HjfaXBMSDj0Na9a3QzbTj6s8eJHECQ3W54WDlc21yf o4AoErgu+XjXrHRfung5XMmjYipL5lyXnf7xrZqiDC8D5kneqB1dPQRL5luj54X8 T9XfRgXv9gfBTquRhLy5nUqCbz88Rp+XxkefhRmk1MAegOAC1bA4+4b7W7HbfikS 1DwsUHKKxxwHX6whQaljyTRt6CZ3Yf7A1/bOVyhzb0WvehzGAX7Bxz2snbDMahbB h22SVCCLoK/2fsWXUuuTo+CDq5zQ0YW9trJiCidytLRjegvWqfpdf5MmkgpizhWm TecD73OdSclDJpGMNbAqSlbnlJbNLDnjD6Xfnq2CQdys+tmxoKbpuAfTGeKG8Ymu qWfinzdcQgE8T9tpPEa3CPD/ApqNTW++e9nqLHSCs+JhqK+eMWCIwAfRRw+QTYAf jADEX9KYUNTU3QRTb1wbIYIFFszdTUuyLnSiKt5B0KeV1Dhz6o848Yo++akLndJP 3iL4Bf6tO+ZIIeFUBoQ3 =f0fK -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Fwd: Apache Tomcat 7 -Parameters lost
kartheek desineedi wrote: Yes we upgraded to Apache Tomcat 7.0.62 but still the issue is persisting. Failed request filter did not filter out any params indicating that the parameters are not malformed. We are sending all the requests in the SAME manner while most of them succeed,few of them fail. Which class in the tomcat source should we try adding more debugging if need be? [...] Kartheek, Extraordinary claims require extraordinary evidence [Carl Sagan] Processing POST requests with parameters is what webservers do 99% of the time, and Tomcat is a webserver, with several hundred thousand installations. If several versions of Tomcat were just losing POST parameters randomly, it seems very unlikely that you would have been the first and only one to have noticed this and posted a message about this on the list. So, without getting very technical about it, I would suggest that there must be another explanation to your problem; and I would further suggest that you re-examine your evidence very carefully. Are you 100% sure that there is nothing in these requests which could prevent a correct parsing of these parameters ? And/or are you sure that when you compare the tcpdump log and the requests that you see in the request dumper log, you are indeed looking at the /same/ requests ? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Fwd: Apache Tomcat 7 -Parameters lost
From: André Warnier [mailto:a...@ice-sa.com] Subject: Re: Fwd: Apache Tomcat 7 -Parameters lost Are you 100% sure that there is nothing in these requests which could prevent a correct parsing of these parameters ? And/or are you sure that when you compare the tcpdump log and the requests that you see in the request dumper log, you are indeed looking at the /same/ requests ? And of course, there's the not unusual webapp logic error of storing a request or response reference somewhere it shouldn't so that it gets used by multiple threads or in multiple requests. The typical spot is a servlet instance field, but thread-locals and static variables are also problematic. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Fwd: Apache Tomcat 7 -Parameters lost
Thanks for your response Christopher. Consecutive requests in the sense when 5(for example) users send requests in the normal transaction flow,one of them fails. The logs at different layers of the request flow indicate that the parameters are being passed from the original request till the AJP port 8009 but in the request dumper logs we do NOT see those parameters. Since our application would receive the requests AFTER the request dumper filter it is obvious that the parameters are lost even before our application gets them. What would be the best log to look at in our case? Is there any additional logging/config that needs to be enabled at Tomcat layer? On Fri, Jun 12, 2015 at 2:33 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Kartheek, On 6/12/15 12:32 PM, kartheek desineedi wrote: We are facing a weird issue where a similar configuration is yielding unexpected results for consecutive requests on Tomcat 7.0.54. We have enabled the request dumper filter on Tomcat 7 and it shows that consecutive requests are missing the parameters. What do you mean consecutive requests? Due to this our application is throwing a backend error and giving a bad user experience of not letting the user complete a transaction. Did anyone face a similar issue on Tomcat 7 ?I can share more configuration files as required to help give more details on the issue. Did you follow-up on all the questions we've already asked, and the ideas we've presented? You have a handful of replies on your earlier thread. Helpful pointers are greatly appreciated. LOG link: http://www.filedropper.com/requestdumper TCP dump -8009 http://www.filedropper.com/tcpdump I looked, and these don't tell me anything. I have no idea what I'm looking at. Additional Info: We are not aware of any specific pattern.The transaction is going through Browser [HTTP | Port 80] Web Server [HTTP | Port 80] Mod JK [AJP 13 | Port 8009] Tomcat [AJP 13 | Port 8009].The parameters are submitted through a form POST.We roughly see this issue once in 5 times.The log which we shared is from the tomcat's request dumper filter which is supposedly the first filter before any of the application level filters are invoked which means that our application is not even receiving them.Hope this gives you a better idea. So, is the RequestDumperFilter seeing the parameters but your application is not? Or are you saying that not even the RequestDumperFilter is seeing the parameters? Added the tcp dump for port 8009 which is the last layer before the request dumper log and the parameters are found in both the cases.(please ignore the file name in the logs) - -chris -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVezQCAAoJEBzwKT+lPKRYZf8QAKsRxMbOHgEsyJIvX6hEgqvY SMnVGSdTaIuwcxUqyvsqzTGdjO2yG3dwZO8otd/IHHOLBVko5s/irAAnYVS0o517 OJFRI0XG1mtaHwVy3Z9xgCvxgL7pSLbLoVBA+5t+zJR28RM3hhc8pRGNB/mZ5gYS FBQGFFJkIwdIN4RZNa4Z38HjfaXBMSDj0Na9a3QzbTj6s8eJHECQ3W54WDlc21yf o4AoErgu+XjXrHRfung5XMmjYipL5lyXnf7xrZqiDC8D5kneqB1dPQRL5luj54X8 T9XfRgXv9gfBTquRhLy5nUqCbz88Rp+XxkefhRmk1MAegOAC1bA4+4b7W7HbfikS 1DwsUHKKxxwHX6whQaljyTRt6CZ3Yf7A1/bOVyhzb0WvehzGAX7Bxz2snbDMahbB h22SVCCLoK/2fsWXUuuTo+CDq5zQ0YW9trJiCidytLRjegvWqfpdf5MmkgpizhWm TecD73OdSclDJpGMNbAqSlbnlJbNLDnjD6Xfnq2CQdys+tmxoKbpuAfTGeKG8Ymu qWfinzdcQgE8T9tpPEa3CPD/ApqNTW++e9nqLHSCs+JhqK+eMWCIwAfRRw+QTYAf jADEX9KYUNTU3QRTb1wbIYIFFszdTUuyLnSiKt5B0KeV1Dhz6o848Yo++akLndJP 3iL4Bf6tO+ZIIeFUBoQ3 =f0fK -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- *Saludos,* Kartheek DVRK http://dreamchannel.bigrock.in
Re: Fwd: Apache Tomcat 7 -Parameters lost
Yes we upgraded to Apache Tomcat 7.0.62 but still the issue is persisting. Failed request filter did not filter out any params indicating that the parameters are not malformed. We are sending all the requests in the SAME manner while most of them succeed,few of them fail. Which class in the tomcat source should we try adding more debugging if need be? On Fri, Jun 12, 2015 at 3:34 PM, kartheek desineedi kartheekdesine...@gmail.com wrote: Thanks for your response Christopher. Consecutive requests in the sense when 5(for example) users send requests in the normal transaction flow,one of them fails. The logs at different layers of the request flow indicate that the parameters are being passed from the original request till the AJP port 8009 but in the request dumper logs we do NOT see those parameters. Since our application would receive the requests AFTER the request dumper filter it is obvious that the parameters are lost even before our application gets them. What would be the best log to look at in our case? Is there any additional logging/config that needs to be enabled at Tomcat layer? On Fri, Jun 12, 2015 at 2:33 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Kartheek, On 6/12/15 12:32 PM, kartheek desineedi wrote: We are facing a weird issue where a similar configuration is yielding unexpected results for consecutive requests on Tomcat 7.0.54. We have enabled the request dumper filter on Tomcat 7 and it shows that consecutive requests are missing the parameters. What do you mean consecutive requests? Due to this our application is throwing a backend error and giving a bad user experience of not letting the user complete a transaction. Did anyone face a similar issue on Tomcat 7 ?I can share more configuration files as required to help give more details on the issue. Did you follow-up on all the questions we've already asked, and the ideas we've presented? You have a handful of replies on your earlier thread. Helpful pointers are greatly appreciated. LOG link: http://www.filedropper.com/requestdumper TCP dump -8009 http://www.filedropper.com/tcpdump I looked, and these don't tell me anything. I have no idea what I'm looking at. Additional Info: We are not aware of any specific pattern.The transaction is going through Browser [HTTP | Port 80] Web Server [HTTP | Port 80] Mod JK [AJP 13 | Port 8009] Tomcat [AJP 13 | Port 8009].The parameters are submitted through a form POST.We roughly see this issue once in 5 times.The log which we shared is from the tomcat's request dumper filter which is supposedly the first filter before any of the application level filters are invoked which means that our application is not even receiving them.Hope this gives you a better idea. So, is the RequestDumperFilter seeing the parameters but your application is not? Or are you saying that not even the RequestDumperFilter is seeing the parameters? Added the tcp dump for port 8009 which is the last layer before the request dumper log and the parameters are found in both the cases.(please ignore the file name in the logs) - -chris -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVezQCAAoJEBzwKT+lPKRYZf8QAKsRxMbOHgEsyJIvX6hEgqvY SMnVGSdTaIuwcxUqyvsqzTGdjO2yG3dwZO8otd/IHHOLBVko5s/irAAnYVS0o517 OJFRI0XG1mtaHwVy3Z9xgCvxgL7pSLbLoVBA+5t+zJR28RM3hhc8pRGNB/mZ5gYS FBQGFFJkIwdIN4RZNa4Z38HjfaXBMSDj0Na9a3QzbTj6s8eJHECQ3W54WDlc21yf o4AoErgu+XjXrHRfung5XMmjYipL5lyXnf7xrZqiDC8D5kneqB1dPQRL5luj54X8 T9XfRgXv9gfBTquRhLy5nUqCbz88Rp+XxkefhRmk1MAegOAC1bA4+4b7W7HbfikS 1DwsUHKKxxwHX6whQaljyTRt6CZ3Yf7A1/bOVyhzb0WvehzGAX7Bxz2snbDMahbB h22SVCCLoK/2fsWXUuuTo+CDq5zQ0YW9trJiCidytLRjegvWqfpdf5MmkgpizhWm TecD73OdSclDJpGMNbAqSlbnlJbNLDnjD6Xfnq2CQdys+tmxoKbpuAfTGeKG8Ymu qWfinzdcQgE8T9tpPEa3CPD/ApqNTW++e9nqLHSCs+JhqK+eMWCIwAfRRw+QTYAf jADEX9KYUNTU3QRTb1wbIYIFFszdTUuyLnSiKt5B0KeV1Dhz6o848Yo++akLndJP 3iL4Bf6tO+ZIIeFUBoQ3 =f0fK -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- *Saludos,* Kartheek DVRK http://dreamchannel.bigrock.in -- *Saludos,* Kartheek DVRK http://dreamchannel.bigrock.in
Re: Fwd: Apache Tomcat 7 -Parameters lost
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Kartheek, On 6/12/15 4:41 PM, kartheek desineedi wrote: Yes we upgraded to Apache Tomcat 7.0.62 but still the issue is persisting. Failed request filter did not filter out any params indicating that the parameters are not malformed. We are sending all the requests in the SAME manner while most of them succeed,few of them fail. Which class in the tomcat source should we try adding more debugging if need be? Can you add this Filter to your web application to see if the problem is that the request itself is badly-formatted in some way? http://tomcat.apache.org/tomcat-7.0-doc/config/filter.html#Failed_Reques t_Filter - -chris On Fri, Jun 12, 2015 at 3:34 PM, kartheek desineedi kartheekdesine...@gmail.com wrote: Thanks for your response Christopher. Consecutive requests in the sense when 5(for example) users send requests in the normal transaction flow,one of them fails. The logs at different layers of the request flow indicate that the parameters are being passed from the original request till the AJP port 8009 but in the request dumper logs we do NOT see those parameters. Since our application would receive the requests AFTER the request dumper filter it is obvious that the parameters are lost even before our application gets them. What would be the best log to look at in our case? Is there any additional logging/config that needs to be enabled at Tomcat layer? On Fri, Jun 12, 2015 at 2:33 PM, Christopher Schultz ch...@christopherschultz.net wrote: Kartheek, On 6/12/15 12:32 PM, kartheek desineedi wrote: We are facing a weird issue where a similar configuration is yielding unexpected results for consecutive requests on Tomcat 7.0.54. We have enabled the request dumper filter on Tomcat 7 and it shows that consecutive requests are missing the parameters. What do you mean consecutive requests? Due to this our application is throwing a backend error and giving a bad user experience of not letting the user complete a transaction. Did anyone face a similar issue on Tomcat 7 ?I can share more configuration files as required to help give more details on the issue. Did you follow-up on all the questions we've already asked, and the ideas we've presented? You have a handful of replies on your earlier thread. Helpful pointers are greatly appreciated. LOG link: http://www.filedropper.com/requestdumper TCP dump -8009 http://www.filedropper.com/tcpdump I looked, and these don't tell me anything. I have no idea what I'm looking at. Additional Info: We are not aware of any specific pattern.The transaction is going through Browser [HTTP | Port 80] Web Server [HTTP | Port 80] Mod JK [AJP 13 | Port 8009] Tomcat [AJP 13 | Port 8009].The parameters are submitted through a form POST.We roughly see this issue once in 5 times.The log which we shared is from the tomcat's request dumper filter which is supposedly the first filter before any of the application level filters are invoked which means that our application is not even receiving them.Hope this gives you a better idea. So, is the RequestDumperFilter seeing the parameters but your application is not? Or are you saying that not even the RequestDumperFilter is seeing the parameters? Added the tcp dump for port 8009 which is the last layer before the request dumper log and the parameters are found in both the cases.(please ignore the file name in the logs) -chris - - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- *Saludos,* Kartheek DVRK http://dreamchannel.bigrock.in -BEGIN PGP SIGNATURE- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVe0i4AAoJEBzwKT+lPKRYE5AP/3KWQvCuFd6A87/tLhzhVBf3 Itc755Kmiv/553bFwRrhg+a2dEEDACaTyfrl1kZBijg5U6nftQkL9GVJU3k/oLDf YaS2hkU1MpWhRbkp8RLxxzz+L0wPFZOw2ao/W8E9gWQRZOMJyYDFxKL0VcAJtTVR C9vgesIYzdN/P74HVsuZJuNo4jgOAG9O+ns8mC5/88k5ob7OULTvDto4m+BAGmTC bOD7hw7eA9CpdU79g5hrd//TLoMrDdrO3BUIbnN5SY0XROV6ceDIUsA0u5rYAuC9 GNsLdP8JvqqOMgCvl24Hu9bA72P8OEa3xQvhwnCFSJlooSAwZJbu6FmnYdymuKjj i77/x0+5z1vSja5Tzpd+lsFfPowq0kvHw3lWcPIA4q9zTDcJzn4PY4hhu+WxWBll tjFQwmxInRbV4P2/v0eyYzUYvbwD4wyik08ceYrPwEjfvoEFhDk28TgrxJggccck bPkP2puCEnPs2+DCoWQrxmNLtJaNbPv8Fu83/wbahf7IWLLu2NVJEa5aFH1I5fnl FWpLwmON/8b9j1G1GDq2p7Sn2jj619jHNk7Hs4fdNUIkrK2Qt1pOFpJqwsDL7Tuq UYt5fn5AweqZwHuAbiCeCVD+MRRx+sJcZxmMEQMMcndiQQVzqvKVwIXGqNQB1kYj RigdeTdAeJs2S08/uqp5 =oDRI -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
