JDK-4685738 : possible problem in CJavaJNI.cpp
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 1.3.1
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2002-05-15
  • Updated: 2002-11-06
  • Resolved: 2002-09-30
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other Other Other Other
1.3.1_07 07Fixed 1.4.0_04Fixed 1.4.1_02Fixed 1.4.2Fixed
Description
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.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.3.1_07 1.4.0_04 1.4.1_02 mantis FIXED IN: 1.3.1_07 1.4.0_04 1.4.1_02 mantis INTEGRATED IN: 1.3.1_07 1.4.0_04 1.4.1_02 mantis mantis-b03
14-06-2004
EVALUATION If the jvm.dll is not loaded by java plug-in, one of the member variable will not be set. Even if we fix this problem, in such scenarios, plug-in specific run time parameters and other initialization will not be done and hence there is no guarantee that the applet works. ###@###.### 2002-05-16
16-05-2002