This content has been marked as final. Show 3 replies
Try with a more recent version of Java I'd say. A more recent version of Java 6 at the very least.1 person found this helpful
And I hope you can hire some expert assistance to support you. If you have any kind of question which can be answered in a forum, which tends to require something actually visible like code, feel free to ask it. But it needs to be a question that can be answered by Java developers and I'm sorry to say even though you're trying to hook into the Java virtual machine - all you are basically going to be able to offer is gobs of C++ code which you won't get very far with here.
We don't expect a Java/JNI exception here as this part of code doesn't make any JNI callYou're running this from a native application aren't you? So you're using the Java Native Interface, only in the reverse direction (the invocation API). You even posted this in the JNI forum so you must have realized it in some way or another. Its not too strange to get a JNI exception, although its hard to say anything definitive since you refuse to share the actual error you're getting.
user2114451 wrote:Is there any JNI calls at all in any way up to that point? If so then it is suspect.
as this part of code doesn't make any JNI call
Is there any dll initialization code at all associated with the JNI including third party libraries? If so then it is suspect.
and moreover the JVM destroy call is successful before reaching this point.At least in the past that did nothing with the Oracle/Sun VM.
We tried the most recent version of Java6 (184.108.40.206) & Java7 (220.127.116.11)
We don't see the issue anymore with Java7 but we see intermittent results with Java6.
Anyways, we would upgrade to Java7 which is more consistent. Thanks for you help.