Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 84529 invoked from network); 23 Nov 2005 23:18:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 23 Nov 2005 23:18:01 -0000 Received: (qmail 20166 invoked by uid 500); 23 Nov 2005 23:17:51 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 20146 invoked by uid 500); 23 Nov 2005 23:17:51 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 20133 invoked by uid 99); 23 Nov 2005 23:17:51 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Nov 2005 15:17:51 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [67.18.92.178] (HELO jbother.org) (67.18.92.178) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Nov 2005 15:19:22 -0800 Received: from [192.168.1.10] (66.239.17.226.ptr.us.xo.net [66.239.17.226]) by jbother.org (Postfix) with ESMTP id BD71B88E0F for ; Wed, 23 Nov 2005 16:17:29 -0700 (MST) Message-ID: <4384F887.2070303@jbother.org> Date: Wed, 23 Nov 2005 16:17:27 -0700 From: Adam Olsen User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: users@httpd.apache.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Subject: [users@httpd] Strange problem X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N We are using perl and apache2 for our software. With our software, our users have the ability to upload an optional 4 images via an html form (sometimes the images can be quite big, they are from digital cameras). While and image is uploading, apache2 queues all other requests until the upload completes. I have confirmed this by watching the process list and attempting to upload a large image. While it's uploading, I can watch the processes stack up. They do this until I hit stop on my browser, and then they all get sent. This is really causing a huge problem, because it's a pretty high volume site, and if someone on dialup is uploading a 1MB image, the server is virtually unuseable. Note that during an image upload, the server's CPU load is usually floating around 90% idle, and there's plenty of memory left. Any ideas on this one would be appreciated. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org