>________________________________________ >From: Jesse Barnum [jsb_tom...@360works.com] >Sent: Thursday, December 26, 2013 2:14 PM >To: Tomcat Users List >Subject: Re: Request Timeout and empty post data issue > >One issue that will cause empty POST data to be received is if the POST data >size exceeds the value in the server.xml file: > >http://tomcat.apache.org/tomcat-7.0-doc/config/ajp.html > >> The maximum size in bytes of the POST which will be handled by the container >> FORM URL parameter parsing. The limit can be disabled by setting this >> attribute to a value less than or equal to 0. If not specified, this >> attribute is set to 2097152 (2 megabytes). > >It would also make sense that these larger POSTs would take longer, so it fits >the evidence. > >--Jesse Barnum, President, 360Works >http://www.360works.com >Product updates and news on http://facebook.com/360Works >(770) 234-9293 >== Don't lose your data! http://360works.com/safetynet/ for FileMaker Server == > >On Dec 26, 2013, at 3:45 PM, Peter Rifel <pri...@mixpo.com> wrote: > >> Hello, >> >> I'm currently running Tomcat 7.0.42 on Ubuntu 12.04 with OpenJDK 1.7.0_25. >> I'm using Apache Tomcat Native library 1.1.27 with APR version 1.4.6. >> >> I'm noticing in my access logs that some of our POST requests don't have any >> POST data and all have response times of a few ms over 20000ms. I'm trying >> to figure out whether this issue is client side or server side. The >> response code and response size for these requests are normal. Can anyone >> tell me under what circumstances this would happen? I noticed that our >> connector's connectionTimeout is set to 20000ms, but it wouldn't make sense >> for that value to be a part of this issue because a connection timeout only >> occurs when the URI hasn't been received by tomcat in that amount of time, >> which is clearly not happening here (I was able to confirm this with telnet; >> a connection timeout will not write anything to the access logs). >> >> The "request" is making it to my servlet (logging confirms this) but for >> some reason tomcat doesn't see any request parameters and all of the >> response times in our access logs are just above 20 seconds. Does this mean >> that my servlet is taking 20 seconds to process the request? Is there some >> other timeout value somewhere that defaults to 20 seconds? Is there a way >> for me to see exactly what is taking so long? Its incredibly hard to debug >> this because we cant reproduce this bug on our own without any post data and >> <1% of our production traffic is having this issue. To try and gather more >> info on this, I added a servlet filter that logs all of our POST request >> parameters to the access log and I can confirm that there are no parameters >> on these specific requests. >> >> The lack of post data makes me think its a client issue, but that doesn't >> explain why all of these requests take ~20 seconds to be processed. >> >> I'd appreciate any ideas on what could cause this. >> >> Thanks, >> >> Peter >>
In this case, these requests are only plaintext, never more than a few hundred characters. Our max post size is set to 10MB so theres no apparent reason that we would reach this limit on these requests, nor is there a reason that processing the data would timeout unless there was a problem with the data itself. Thanks for the suggestion, Peter --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
