Return-Path: Delivered-To: apmail-perl-embperl-archive@www.apache.org Received: (qmail 53582 invoked from network); 20 Sep 2004 10:06:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 20 Sep 2004 10:06:15 -0000 Received: (qmail 49815 invoked by uid 500); 20 Sep 2004 10:06:03 -0000 Delivered-To: apmail-perl-embperl-archive@perl.apache.org Received: (qmail 49730 invoked by uid 500); 20 Sep 2004 10:06:02 -0000 Mailing-List: contact embperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Delivered-To: mailing list embperl@perl.apache.org Received: (qmail 49646 invoked by uid 99); 20 Sep 2004 10:06:00 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [212.87.33.16] (HELO nexus.combox.de) (212.87.33.16) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 20 Sep 2004 03:06:00 -0700 Received: from combox.de ([212.87.33.8] helo=welt.combox.de) by nexus.combox.de with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.42) id 1C9L3V-00042i-9G for embperl@perl.apache.org; Mon, 20 Sep 2004 12:05:57 +0200 Received: from [192.168.1.198] (helo=[192.168.1.198]) by welt.combox.de with esmtps (Exim 4.42 1) id 1C9L3U-00077w-Ep for ; Mon, 20 Sep 2004 12:05:56 +0200 Subject: RE: httpd stalling. From: Mailinglisten To: embperl@perl.apache.org In-Reply-To: <20040919122245.212DF1AB664@lnx1.i.ecos.de> References: <20040919122245.212DF1AB664@lnx1.i.ecos.de> Content-Type: text/plain Message-Id: <1095675000.14245.2.camel@install.cff> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Mon, 20 Sep 2004 12:10:00 +0200 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On So, 2004-09-19 at 14:22, Gerald Richter wrote: > Maybe it helps to switch to the MySQL lock meachnisem, instead of using > semaphores, because it works a little different when aquiring locks I made similar experiences with the semaphore locking method. It caused two different problems for me: * deadlocks like the ones you experienced * if two users concurrently use the site, the results appear simultaneously; i.e. the one with the faster access has to wait till the other one has finished. This was a big problem for us. Now, I switched to "sessions in files, use files for locking" and the problems vanished. Cannot say what mysql locking will do, I never used a database for session storage. Greetings, Torsten --------------------------------------------------------------------- To unsubscribe, e-mail: embperl-unsubscribe@perl.apache.org For additional commands, e-mail: embperl-help@perl.apache.org