Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2054675 | 1.4.2 | Devananda Jayaraman | P4 | Resolved | Fixed | mantis |
JDK-2054674 | 1.4.1_02 | Devananda Jayaraman | P4 | Resolved | Fixed | 02 |
JDK-2054673 | 1.4.0_04 | Devananda Jayaraman | P4 | Resolved | Fixed | 04 |
From talking with my friends at SAS and from poking around in the code
I believe I have found a problem in CJavaJNI.cpp.
The routine:
jint CJavaJNI::JNI_GetCreatedJavaVMs(JavaVM **vmp, jsize bufLen ,jsize *nVMS) {
JVM_GETCREATED proc;
proc =(JVM_GETCREATED) GetProcAddress(m_hMod, "JNI_GetCreatedJavaVMs");
return proc != 0 ? (*proc)(vmp, bufLen, nVMS) : -1;
}
uses the variable `m_hMod', which is not set (it is an auto variable).
So, my idea is to set `m_hMod' in `LoadJavaVM'.
If you start the JVM from jpishare.dll you will not see this
problem. This might explain why we have gone so far without running
into this yet.
- backported by
-
JDK-2054673 possible problem in CJavaJNI.cpp
- Resolved
-
JDK-2054674 possible problem in CJavaJNI.cpp
- Resolved
-
JDK-2054675 possible problem in CJavaJNI.cpp
- Resolved