https://bugzilla.novell.com/show_bug.cgi?id=221420 ------- Comment #3 from jluciani@novell.com 2006-11-16 09:16 MST ------- Hi Daniel, I looked at the bug referenced above and I do not believe is related. There are a couple of things with regards to that bug that do not seem right. First issue with referenced bug: The submitted code has an issue that could be the source of the problem (the code uses the jclass and jmethodID objects obtained using the JNIEnv object created from the main thread when calling into the JNIEnv object created in the worker thread, my understanding is that the code should call into a JNIEnv object using objects that it obtained from it). Second issue with referenced bug: The response from the Sun support engineer "that since thread in question was created by c++ and not java, the thread does not have any information about java context which a java create thread might have" does not agree with the Sun's documentation (http://java.sun.com/j2se/1.4.2/docs/guide/jni/spec/invocation.html) which states that "The JNI interface pointer (JNIEnv) is valid only in the current thread. Should another thread need to access the Java VM, it must first call AttachCurrentThread() to attach itself to the VM and obtain a JNI interface pointer. Once attached to the VM, a native thread works just like an ordinary Java thread running inside a native method. The native thread remains attached to the VM until it calls DetachCurrentThread() to detach itself." Thanks for your help, Juan Carlos -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.