From dev-return-70901-apmail-ant-dev-archive=ant.apache.org@ant.apache.org Mon Jan 30 17:45:11 2006 Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 65496 invoked from network); 30 Jan 2006 17:45:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 30 Jan 2006 17:45:11 -0000 Received: (qmail 40070 invoked by uid 500); 30 Jan 2006 17:45:10 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 39826 invoked by uid 500); 30 Jan 2006 17:45:08 -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 39814 invoked by uid 99); 30 Jan 2006 17:45:08 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jan 2006 09:45:08 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [192.6.10.2] (HELO colossus.hpl.hp.com) (192.6.10.2) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jan 2006 09:45:07 -0800 Received: from kropotkin.hpl.hp.com (kropotkin.hpl.hp.com [15.144.59.2]) by colossus.hpl.hp.com (8.12.10/8.12.10) with ESMTP id k0UHiLcv029092 for ; Mon, 30 Jan 2006 17:44:21 GMT Received: from localhost (localhost [127.0.0.1]) by kropotkin.hpl.hp.com (Postfix) with ESMTP id A3996A4A1 for ; Mon, 30 Jan 2006 17:44:21 +0000 (GMT) Received: from kropotkin.hpl.hp.com ([127.0.0.1]) by localhost (kropotki [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 13907-02-8 for ; Mon, 30 Jan 2006 17:44:17 +0000 (GMT) Received: from timmay.hpl.hp.com (timmay-hb.hpl.hp.com [15.144.59.39]) by kropotkin.hpl.hp.com (Postfix) with ESMTP id B32E177B5 for ; Mon, 30 Jan 2006 17:44:17 +0000 (GMT) Received: from [16.27.193.160] ([16.27.193.160]) by timmay.hpl.hp.com (8.13.2/8.13.2) with ESMTP id k0UHiDlT014972 for ; Mon, 30 Jan 2006 17:44:13 GMT Message-ID: <43DE5094.60805@apache.org> Date: Mon, 30 Jan 2006 17:44:52 +0000 From: Steve Loughran User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ant Developers List Subject: Re: and exit code 128 References: <43DA1437.9050006@imapmail.org> In-Reply-To: <43DA1437.9050006@imapmail.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-HPLB-IMAP-MailScanner-Information: Please contact the Helpdesk for more information X-HPLB-IMAP-MailScanner: Found to be clean X-HPLB-IMAP-MailScanner-SpamCheck: not spam, SpamAssassin (score=0, required 5) X-Virus-Scanned: amavisd-new at kropotkin.hpl.hp.com X-HPL-MailScanner-Information: Please contact the Helpdesk for more information X-HPL-MailScanner: Found to be clean X-HPL-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.958, required 5, autolearn=not spam, AWL 0.64, BAYES_00 -2.60) X-MailScanner-From: stevel@apache.org X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N 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... --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org