Magnus said the following on 02/09/2011 03:32 PM: > Apache 2.2.11 > Tomcat 6.0.20 > AJP proxying to connect Apache and Tomcat > OpenBD 1.4 > CentOS release 4.8 (Final) > > Not all big requests throw an error. Less sure about whether long > running requests do based on the info I have now. There is probably a request size limit -- you'd know about that - because it would consistent. I think the issue is less of size and more about time. A client could exceed a request timeout before sending a file at 30kb/s instead of 3Mb/s. So I think that's why you're seeing random file sizes that throws.
Take a peek at your Apache logs. Do you see anything like: [Thu Nov 20 10:53:45 2008] [error] (70007)The timeout specified has expired: ajp_ilink_receive() can't receive header [Thu Nov 20 10:53:45 2008] [error] ajp_read_header: ajp_ilink_receive failed [Thu Nov 20 10:53:45 2008] [error] (120006)APR does not understand this error code: proxy: read response failed from 127.0.0.1:7009 (localhost) The default amount of time Apache mod_proxy_ajp waits for the servlet to complete request it is proxying is 300 seconds. My guess is that your client is taking more that 300 seconds to upload the file. You can use the proxyTimeout directive to increase this timeout: http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxytimeout Also, Tomcat itself has it's own timeouts: http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html HTH, .Peter -- tag/function ref: http://www.openbluedragon.org/manual/ mailing list - http://groups.google.com/group/openbd?hl=en Get to Texas in Feb for OpenCFSummit http://www.opencfsummit.org/
