Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a web application that traditionally ran on Windows Server 2003 Std. Ed. 32bit in Apache2.2 with perl 5.8. I am attempting to migrate it to a Windows Server 2008 Std. Ed. 64bit in Apache2.2 with perl 5.10 platform. It ran great on the old platform, but now I am having memory issues.

In the httpd.conf I have:

ThreadLimit 20
ThreadsPerChild 20
MaxRequestsPerChild 10000

In Windows Task Manager there are currently 20 instances of "perl.exe *32" using around 24,000K of memory a piece. The number of instances grows or shrinks with the Thread Limit, but it never drops below the limit. The application is technically up and running, but it is just very, very slow. We are using the same httpd.conf in both platforms. Could this be related to switching to perl 5.10, or switching to a 64bit version of windows, and how do I correct it?

share|improve this question
up vote 1 down vote accepted

You might have

RequestHeader unset Connection
RequestHeader unset Server

set in your config file. Remove those and the issue should go away.

share|improve this answer
That was it! I commented out those lines and now it works. How did you know? – Jason Lamoreux Jan 26 '10 at 19:01
My boss saw the issue once before and he told me about it. – Frew Schmidt Jan 26 '10 at 19:02

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.