I've (hopefully) eliminated the network itself as a source of the problem by testing this with the app server running on the same box as apache, using 127.0.0.1 as the network address in the proxy config.
Even like this, I still get occasional '(70007)The timeout specified has expired: proxy: prefetch request body failed to 127.0.0.1:4000 (127.0.0.1)' messages in the logs.
The app server shows the socket accept happening at the point the request is made, but then just sticks in a select() call until the timeout occurs (set to 5 seconds). No data is recieved from the apache mod_proxy.
The apache logs then get the error message shown above added to them.The connection that mod_proxy is using is plain http, not https. This seems to happen maybe once or twice a day, no apparent pattern with system load, client type, url being requested etc.
Is there anywhere that details the different error log messages that mod_proxy can generate, what they actually mean, and possible causes of them. I'm not even sure in this case if 'prefetch request body failed' relates to getting data from the app server or getting it from the web browser client (the error has 'to 127.0.0.1' in it which makes me think it relates to getting data from the app server)
Is there any enhanced logging I can add to mod_proxy, for example to show it making the connection, packets sent, packets recieved etc. I just can't see why this timeout fails with mod_proxy not sending any data to the app server. Does mod proxy need the entire request from the browser before it forwards it on (what about requests with large post data? - though that is not the case in these errors). Can it have a long delay between making the connection to the app server and actually starting to transmit the request?
Thanks for any hints/tips. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|