Return-Path: X-Original-To: apmail-tomcat-dev-archive@www.apache.org Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5A33810C2E for ; Fri, 3 May 2013 15:02:24 +0000 (UTC) Received: (qmail 18080 invoked by uid 500); 3 May 2013 15:02:23 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 17968 invoked by uid 500); 3 May 2013 15:02:23 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 17954 invoked by uid 99); 3 May 2013 15:02:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 May 2013 15:02:23 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of awang@ptc.com designates 12.11.148.84 as permitted sender) Received: from [12.11.148.84] (HELO irp2.ptc.com) (12.11.148.84) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 May 2013 15:02:14 +0000 X-IronPort-AV: E=Sophos;i="4.87,605,1363147200"; d="scan'208,217";a="148161012" Received: from hq-x10prdhub2.ptcnet.ptc.com ([132.253.198.28]) by irp2.ptc.com with ESMTP; 03 May 2013 11:01:51 -0400 Received: from awang.ptcnet.ptc.com (132.253.198.6) by int-mail.ptc.com (132.253.198.28) with Microsoft SMTP Server id 14.2.309.2; Fri, 3 May 2013 11:01:51 -0400 Message-ID: <5183D15A.30001@ptc.com> Date: Fri, 3 May 2013 10:01:46 -0500 From: Andy Wang User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130402 Thunderbird/17.0.5 MIME-Version: 1.0 To: Subject: Re: Problem with nsapi_redirect.so (1.2.37) on iPlanet 7.0.15 and Solaris 11 References: <5122A185.6080408@ptc.com> <5123177A.2050100@apache.org> <51239BE5.1010701@ptc.com> <5123B2C0.8010001@kippdata.de> <51269C2C.3060307@ptc.com> <5182985B.4060408@ptc.com> <5182B0DF.2000004@kippdata.de> In-Reply-To: <5182B0DF.2000004@kippdata.de> Content-Type: multipart/alternative; boundary="------------070409050304050707090208" X-Originating-IP: [132.253.198.6] X-Virus-Checked: Checked by ClamAV on apache.org --------------070409050304050707090208 Content-Type: text/plain; charset="ISO-8859-15"; format=flowed Content-Transfer-Encoding: 7bit On 05/02/2013 01:30 PM, Rainer Jung wrote: > Especially since the nsapi docs for systhread_start only tell us that > the prio is an int depending on the platform and the only other source > of information, nsapi.h only contains a single defined prio, which is > SYSTHREAD_DEFAULT_PRIORITY. The other constants PR_PRIORITY_... are > defined in nspr/prthread.h and are enum elements of type > PRThreadPriority which formally don't qualify as arguments to > systhread_start(int prio, int stksz, void (*fn)(void *), void *arg) > which needs an int. Yeah, I didn't go as far as dealing with the type differences when complaining to them but I'll make that point as well when I update the call later today. > I'm still not fully convinced, that PR_PRIORITY_* is correct and isn't > just working because PR_PRIORITY_NORMAL=1 is such a low number. When > you use PR_PRIORITY_NORMAL, can you see which priority the created > thread actually has? Probably using truss, since I think the thread > doesn't live long enough to be observable using "ps" with the "-L" > flag for threads and adding "pri" to the output format. Nevertheless > opening a bugzilla seems to be OK for tracking our progress on this > and making the problem publicly available. We might later decide on > resolving it as invalid though ;) Oh absolutely. I actually looked at the NSPR code and found the chunk that does the conversion and at initial glance it's basically the math used allows PR_PRIORITY_NORMAL and LOW to work. I went ahead and filed this in bugzilla: https://issues.apache.org/bugzilla/show_bug.cgi?id=54923 I'll push this with Oracle, but if they refuse to budge, does it seem like there'd be no choice but to include an ugly hack to use PR_PRIORITY_NORMAL or something else? Thanks, Andy --------------070409050304050707090208--