Return-Path: 
 <tomcat-dev-return-51381-apmail-jakarta-tomcat-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-dev-archive@www.apache.org
Received: (qmail 91660 invoked from network); 10 Oct 2004 22:45:36 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 10 Oct 2004 22:45:36 -0000
Received: (qmail 82259 invoked by uid 500); 10 Oct 2004 22:45:26 -0000
Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org
Received: (qmail 81977 invoked by uid 500); 10 Oct 2004 22:45:24 -0000
Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:tomcat-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:tomcat-dev-help@jakarta.apache.org>
List-Post: <mailto:tomcat-dev@jakarta.apache.org>
List-Id: "Tomcat Developers List" <tomcat-dev.jakarta.apache.org>
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Delivered-To: mailing list tomcat-dev@jakarta.apache.org
Received: (qmail 81962 invoked by uid 99); 10 Oct 2004 22:45:24 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=NO_REAL_NAME
X-Spam-Check-By: apache.org
Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10)
  by apache.org (qpsmtpd/0.28) with SMTP; Sun, 10 Oct 2004 15:45:23 -0700
Received: (qmail 26321 invoked by uid 50); 10 Oct 2004 22:47:20 -0000
Date: 10 Oct 2004 22:47:20 -0000
Message-ID: <20041010224720.26320.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 31624] New:  -
    Incomplete error message: java.util.zip.ZipException: No such file or
 directory
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31624>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31624

Incomplete error message: java.util.zip.ZipException: No such file or directory

           Summary: Incomplete error message: java.util.zip.ZipException: No
                    such file or directory
           Product: Tomcat 5
           Version: 5.0.27
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: minfrin@sharp.fm


On startup, tomcat bombs out like so:

Bootstrap: Class loader creation threw exception
java.lang.IllegalArgumentException: addRepositoryInternal
        at
org.apache.catalina.loader.StandardClassLoader.addRepositoryInternal(StandardClassLoader.java:957)
        at
org.apache.catalina.loader.StandardClassLoader.<init>(StandardClassLoader.java:153)
        at
org.apache.catalina.startup.ClassLoaderFactory.createClassLoader(ClassLoaderFactory.java:189)
        at
org.apache.catalina.startup.Bootstrap.createClassLoader(Bootstrap.java:160)
        at
org.apache.catalina.startup.Bootstrap.initClassLoaders(Bootstrap.java:104)
        at org.apache.catalina.startup.Bootstrap.init(Bootstrap.java:193)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:399)
Caused by: java.util.zip.ZipException: No such file or directory
        at java.util.zip.ZipFile.open(Native Method)
        at java.util.zip.ZipFile.<init>(ZipFile.java:112)
        at java.util.jar.JarFile.<init>(JarFile.java:127)
        at java.util.jar.JarFile.<init>(JarFile.java:65)
        at
org.apache.catalina.loader.StandardClassLoader.addRepositoryInternal(StandardClassLoader.java:944)
        ... 6 more

The reason for the error is a missing jar file.

Of course the mystery remains as to WHICH jar file, because the error message
above neglects to mention which jar file.

This leaves the user with the following options:

- Spend hours randomly shooting in the dark trying to find which jar is missing
- Spend hours setting up tomcat in a debugging environment to set a breakpoint
so that it can be seen which jar is missing.

The fix: Include the name of the jar file in the error message.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org