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

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13331

Class loader attempts to open directory as file

           Summary: Class loader attempts to open directory as file
           Product: Tomcat 4
           Version: 4.0.4 Final
          Platform: PC
        OS/Version: OS/2
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


When attempting to start Tomcat 4.04 under OS/2, startup fails with

java.util.zip.ZipException: The file or directory specified is read-only.
        at java.util.zip.ZipFile.open(Native Method)
        at java.util.zip.ZipFile.<init>(ZipFile.java:127)
        at java.util.jar.JarFile.<init>(JarFile.java:138)
        at java.util.jar.JarFile.<init>(JarFile.java:80)
        at
org.apache.catalina.loader.StandardClassLoader.addRepositoryInternal(StandardClassLoader.java:1216)
        at
org.apache.catalina.loader.StandardClassLoader.<init>(StandardClassLoader.java:221)
        at
org.apache.catalina.startup.ClassLoaderFactory.createClassLoader(ClassLoaderFactory.java:204)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:153)
Bootstrap: Class loader creation threw exception
java.lang.IllegalArgumentException: addRepositoryInternal:
java.util.zip.ZipException: The file or directory specified is read-only.
        at
org.apache.catalina.loader.StandardClassLoader.addRepositoryInternal(StandardClassLoader.java:1246)
        at
org.apache.catalina.loader.StandardClassLoader.<init>(StandardClassLoader.java:221)
        at
org.apache.catalina.startup.ClassLoaderFactory.createClassLoader(ClassLoaderFactory.java:204)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:153)

This occurs because Tomcat class loader attempts to open the classes directory
as a file.  Without looking at the Tomcat code, I suspect its attempting to
check if the directory exists.  OS/2 does not allow directories to be opened as
a files.

A temporary workaround is to rename the classes directories so that file open fails.

Thanks

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to