Re: Assistance determining cause of httpd error log entries

2010-11-18 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David, On 11/18/2010 10:42 AM, David Dabbs wrote: > We're using mod_proxy_ajp. I'm considering adding the following to my Apache > & Tomcat configs > In Apache httpd.confProxyIOBufferSize 19456 # like max_packet_size > I think > LimitRequestF

Re: Assistance determining cause of httpd error log entries

2010-11-18 Thread David Dabbs
On Thu, Nov 18, 2010 at 8:52 AM, Christopher Schultz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > David, > > On 11/18/2010 3:41 AM, David Dabbs wrote: > > We're fronting a Tomcat 6.0.29 instance with httpd 2.2.15 via > mod_proxy_ajp. > > Obligatory question: is it really necessary

Re: Assistance determining cause of httpd error log entries

2010-11-18 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David, On 11/18/2010 3:41 AM, David Dabbs wrote: > We're fronting a Tomcat 6.0.29 instance with httpd 2.2.15 via mod_proxy_ajp. Obligatory question: is it really necessary to use httpd at all? > My suspicion is that we get requests with too-long req

Assistance determining cause of httpd error log entries

2010-11-18 Thread David Dabbs
Hello. I have a number of error_log entries I’m trying to resolve. We're fronting a Tomcat 6.0.29 instance with httpd 2.2.15 via mod_proxy_ajp. My suspicion is that we get requests with too-long request uri and or Referrer and this is gumming up the works for AJP protocol marshalling. Would a