Hi,

The problem (actually slightly different but feels the same) is happening
again. The magical trick of unpacking jars isn't going to work, this time,
because my jars are already unpacked :(

What's happening is basically that in the initialization of my app I read
a config file that contains class names.  I've checked several times by
several different methods that the class actually does exist.
(System.out.println the class name immediately before attempting to load
it; cut-n-paste that class name into javap and a little test proggy I
wrote. Both find the class no problem.)

The exception describes itself as this:

java.lang.ClassNotFoundException: java.io.IOException: Bad file descriptor

I don't understand :(

Thanks for your help,
dstn.

Here's the stack trace of that exception:
        at java.io.FileInputStream.readBytes(Native Method)
        at java.io.FileInputStream.read(FileInputStream.java:185)
        at sun.misc.Resource.getBytes(Resource.java:71)
        at java.net.URLClassLoader.defineClass(URLClassLoader.java:245)
        at java.net.URLClassLoader.access$1(URLClassLoader.java:216)
        at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:191)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:280)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:275)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:237)
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:124)
        ...at my code


----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to