Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 74476 invoked from network); 31 Mar 2009 07:01:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 31 Mar 2009 07:01:45 -0000 Received: (qmail 26985 invoked by uid 500); 31 Mar 2009 07:01:45 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 26877 invoked by uid 500); 31 Mar 2009 07:01:44 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 26869 invoked by uid 99); 31 Mar 2009 07:01:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Mar 2009 07:01:44 +0000 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [195.227.30.149] (HELO mailserver.kippdata.de) (195.227.30.149) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Mar 2009 07:01:35 +0000 Received: from [195.227.30.209] (notebook-rj [195.227.30.209]) by mailserver.kippdata.de (8.13.5/8.13.5) with ESMTP id n2V71FU6023245 for ; Tue, 31 Mar 2009 09:01:15 +0200 (CEST) Message-ID: <49D1BF5D.6040808@kippdata.de> Date: Tue, 31 Mar 2009 08:59:41 +0200 From: Rainer Jung User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2 MIME-Version: 1.0 To: APR Development List Subject: Re: Posix sems still not recommended? References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 30.03.2009 20:58, Jeff Trawick wrote: > On Mon, Mar 30, 2009 at 2:33 PM, Jeff Trawick > wrote: > > > > On Mon, Mar 30, 2009 at 2:07 PM, Jim Jagielski > wrote: > > Anyone know if: > > # POSIX semaphores and cross-process pthread mutexes are not # used > by default since they have less desirable behaviour when # e.g. a > process holding the mutex segfaults. > > is still applicable, at least for posix sems? > > > AFAIK, the Solaris-specific recovery logic for cross-process pthread > mutexes has been working reliably for a long time, but with the > current wind direction APR is choosing fcntl(), which has sysdef > implementations on that > > > ugh; "sysdef implications" and quite often shows EDEADLOCK, even when you can prove there can't be one. Especially when starting to use more than one lock of that type (e.g. when SSL comes into the game). > platform. > > no clues here about the POSIX semaphores I would be much interested in an answer as well. Because of the EDEADLOCK problems I did suggest using the pthread based mutex on Solaris for a while to people and got no problem reports. But what experience do others have? In a related thread on the Tomcat users list about mod_jk I wrote in February: I now did some searching and it turns out that the implementation of pthread mutexes for Solaris 10 has very recently changed quite a bit. So all speculations about improved pthread mutex behaviour (especially for "robust" mutexes) in the last years might have become obsolete. The new implementation is contained in Solaris kernel patch 137137-09 and most likely also in Solaris 10 Update 6 (10/08). I didn't check, whether that update simply contains the kernel patch or the fix is included independently. Some detail is logged in Sunsolve under the bug IDs 6296770 2160259 6664275 6697344 6729759 6564706 Regards, Rainer