Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 36285 invoked from network); 31 Jan 2006 11:37:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 31 Jan 2006 11:37:00 -0000 Received: (qmail 86516 invoked by uid 500); 31 Jan 2006 11:36:58 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 86456 invoked by uid 500); 31 Jan 2006 11:36:57 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 86445 invoked by uid 99); 31 Jan 2006 11:36:56 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Jan 2006 03:36:56 -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 [66.111.4.28] (HELO out4.smtp.messagingengine.com) (66.111.4.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Jan 2006 03:36:56 -0800 Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id C0D01D30CA8 for ; Tue, 31 Jan 2006 06:36:34 -0500 (EST) Received: from frontend2.messagingengine.com ([10.202.2.151]) by frontend1.internal (MEProxy); Tue, 31 Jan 2006 06:36:34 -0500 X-Sasl-enc: UEYP8K0y3xBuAiVXunIjX7lvqzhyOE+l4KklssmoTAnL 1138707394 Received: from [172.16.155.140] (host81-137-17-106.in-addr.btopenworld.com [81.137.17.106]) by www.fastmail.fm (Postfix) with ESMTP id 071B857146D for ; Tue, 31 Jan 2006 06:36:33 -0500 (EST) Message-ID: <43DF4B36.9030602@imapmail.org> Date: Tue, 31 Jan 2006 11:34:14 +0000 From: Rob Oxspring User-Agent: Thunderbird 1.4 (Windows/20050908) MIME-Version: 1.0 To: Ant Developers List Subject: Re: and exit code 128 References: <43DA1437.9050006@imapmail.org> <43DE5094.60805@apache.org> In-Reply-To: <43DE5094.60805@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 X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Steve Loughran wrote: > Rob Oxspring wrote: >> Hi, >> >> I've been having problems with the signjar task occasionally failing >> with "exec returned: 128" for a long time now. The problem isn't >> always reproducible and often disappears by simply cleaning the build >> area and starting again; sometimes this technique doesn't work though. >> >> I checked the jarsigner sources and they simply have exit codes of 0 >> and 1 to indicate success and failure, so jarsigner is presumably not >> to blame. From a little googling it looks like this might be a >> cmd.exe issue as there is a generic Windows error message associated >> with 128 that seems relevant: >> >> C:\>net helpmsg 128 >> >> There are no child processes to wait for. >> >> I'm guessing this means that the jarsigner.exe is completing really >> quickly, although I suppose it could mean that it wasn't launched at >> all. I'd really like to get this problem solved as it would make our >> build server that bit more reliable. >> >> Has anyone else seen this sort of thing happening before? any >> recommended solutions? do I just add an ignoreexitcode128 attribute to >> the signjar/exectask? > > Not seen this, and we do a lot of signing; it may depend on jar size. > Now, sometimes java runtimes return funny numbers, so, say HPUX returns > 255 instead of -1. But that is an OS issue, which we would have > encountered on windows before... > I've been looking into this some more and it turns out that our development boxes very rarely suffer this problem while the build server is the only one that sometimes does... I suspect this is due to the build server having twin processors. To test this I've set the processor affinity to make the builds use one processor only and things seem to be working out. It'd be great if there were a solution that'd let us use both processors but I'll have to ponder that for a while. Thanks for you time, Rob --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org