I get the next error occasionally on my small server:

**Proxy Error** 
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /.
Reason: Error reading from remote server

The mistake logs show the next:

[Sun Feb 06 03:06:00 2011] [error] [client 82.43.154.57] proxy: Error reading from remote server returned by /login, referer: https://demo.XXXXX.us/
[Sun Feb 06 03:06:30 2011] [error] [client 82.43.154.57] (70007)The timeout specified has expired: proxy: error reading status line from remote server XXXXX.us
[Sun Feb 06 03:06:30 2011] [error] [client 82.43.154.57] proxy: Error reading from remote server returned by /
[Sun Feb 06 03:13:31 2011] [error] [client 82.43.154.57] (70007)The timeout specified has expired: proxy: error reading status line from remote server XXXXX.us
[Sun Feb 06 03:13:31 2011] [error] [client 82.43.154.57] proxy: Error reading from remote server returned by /

I've read lots of posts recommending connection timeout configurations in tomcat and atmosphere configurations in Apache. I've set the next in httpd.conf:

<VirtualHost *>
   SetEnv force-proxy-request-1.0 1
   SetEnv proxy-nokeepalive 1
</VirtualHost>

I've also set the next in tomcat server.xml:

<Connector port="9080" maxHttpHeaderSize="8192"
               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
               enableLookups="false" redirectPort="9443" acceptCount="100"
               connectionTimeout="60000" disableUploadTimeout="true" />

Also, when the error happens, I must begin a new browser for that error to vanish because it is constantly on the show even on the refresh. Next, I'm using htaccess to rewrite the url. Have no idea if the has any effect on the mistake?

EDIT> My server is running on 150mb of free memory at normal occasions and may drop very reasonable although not in the exact occasions of the aforementioned error. Would this cause this kind of error?

I'd appreciate any ideas individuals have.

Thanks.

This was a problem with Pear Mailer.

I was using Pear Mailer which utilizes a queue to stack emails ready for delivering having a cron job. There is a mistake within the Pear script that was being known as on every action on our website (making posts, delivering messages etc..). Pear was crashes which crashed the browser inducing the above errors.

Crippling Pear resolved the issue, and fine-tuning the code first got it working again.

It required such a long time to obtain the problem once we i never thought Pear Mailer might cause this type of response.