> Bernd Kreimeier <[EMAIL PROTECTED]> writes:
> > My infamous inload test (see http://www.netaccess.ie/~bk/jdkjni/)
> Shouldn't that be http://www.netaccess.ie/~bk/jdk/ ?
Nope, that's an older revision. I separated the JDK JNI test
from the Japhar JNI one, as they have different problems.
But I messed up the location, sorry about that. It should be up
now.
> Yes, you have to tell the VM where it can find classes.zip.
I have a CLASSPATH environment variaable set. The default
vm_args classpath variable seems broken ("/../.."). What am
I missing? I could simply replace the default classpath
entirely, if this is supposed to be invalid.
> You know that that the JNI Invocation API is documented not to work
> with green threads?
Nope. Where is that documented? I must have missed that. In
the May 1997 specs of JNI?
> The green threads' libjava.so overrides some system calls, so the
> first thing in a green threads program must be creating the vm otherwise
> system calls like open() will not work properly.
Aahh. This is an information I could have used 3 weeks ago. Darn.
> You should go to a solaris machine and test your code with native threads.
> (I find some time I will try with Solaris 2.6 and JDK-1.1.6 native threads).
Not that easy. Friend of mine will test this. I was under the
impression that green_threads are used on Solaris, too.
> We really need a native threads vm for linux.
I definitely agree. Wish I had more experience with Linux
threads. Has anybody tried already? Japhar uses native
threads, so it shouldn't be a "dream" by default (as the
FAQ puts it).
Thanks heaps for the info. This is the first inkling in a good
month on what I'm missing.
b.
