Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 51163 invoked from network); 21 Aug 2006 19:08:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 21 Aug 2006 19:08:30 -0000 Received: (qmail 18227 invoked by uid 500); 21 Aug 2006 19:08:29 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 18208 invoked by uid 500); 21 Aug 2006 19:08:29 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 18199 invoked by uid 99); 21 Aug 2006 19:08:29 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Aug 2006 12:08:29 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Aug 2006 12:08:28 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id D5B197142F0 for ; Mon, 21 Aug 2006 19:05:14 +0000 (GMT) Message-ID: <24147327.1156187114872.JavaMail.jira@brutus> Date: Mon, 21 Aug 2006 12:05:14 -0700 (PDT) From: "Doug Cutting (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Resolved: (HADOOP-464) Troubleshooting message for RunJar (bin/hadoop jar) In-Reply-To: <31480789.1155947957107.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 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 [ http://issues.apache.org/jira/browse/HADOOP-464?page=all ] Doug Cutting resolved HADOOP-464. --------------------------------- Fix Version/s: 0.6.0 Resolution: Fixed I committed this, although implemented slightly differently. Rather than printing a message to standard error to amend the uninformative exception, I instead improved the exception. Now the output looks like: % bin/hadoop jar foo Exception in thread "main" java.io.IOException: Error opening job jar: foo at org.apache.hadoop.util.RunJar.main(RunJar.java:82) Caused by: java.util.zip.ZipException: No such file or directory at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.(ZipFile.java:203) at java.util.jar.JarFile.(JarFile.java:132) at java.util.jar.JarFile.(JarFile.java:70) at org.apache.hadoop.util.RunJar.main(RunJar.java:80) > Troubleshooting message for RunJar (bin/hadoop jar) > --------------------------------------------------- > > Key: HADOOP-464 > URL: http://issues.apache.org/jira/browse/HADOOP-464 > Project: Hadoop > Issue Type: Improvement > Components: util > Reporter: Michel Tourn > Fix For: 0.6.0 > > Attachments: runjar.patch > > > Many users get this exception when using bin/hadoop > There are various reasons: > HADOOP_CONF_DIR or HADOOP_HOME misconfigured. > "hadoop jar" parameter incorrect > So the patch displays the path of the jar it is trying to open if this fails: > Problem while opening hadoop job jar: /home/build/hadoop-streaming.jar > Exception in thread "main" java.util.zip.ZipException: error in opening zip file > at java.util.zip.ZipFile.open(Native Method) > at java.util.zip.ZipFile.(ZipFile.java:203) > at java.util.jar.JarFile.(JarFile.java:132) > at java.util.jar.JarFile.(JarFile.java:70) > at org.apache.hadoop.util.RunJar.main(RunJar.java:80) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira