JDK-6644857 : New Plug-In does not call preJVMStart()
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u10
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: windows,windows_xp
  • CPU: generic
  • Submitted: 2007-12-21
  • Updated: 2010-09-08
  • Resolved: 2008-01-31
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.
6u10 b11Fixed
Related Reports
Duplicate :  
Relates :  
The new plug-in is not calling preJVMStart() in kernel.dll prior to JVM start, which means that the kernel will not complete itself when lauched from the new plug-in.

See the old plug-in's preJVMStart() call for an example.

EVALUATION This fix introduced a regression in the initialization of the Firefox port of the plug-in which is described and fixed in 6647070.

SUGGESTED FIX http://sa.sfbay.sun.com/projects/deployment_data/6u10/6644857.0

EVALUATION Added call to preJVMStart() using essentially the same code as the old Java Plug-In. Tested manually to ensure function is being called correctly. Also expanded buffers from MAX_PATH (a very small value) to MAX_BUFFER (1024), specified in src/common/windows/native/common.h, and fixed a typo in the call to FixupJVMPath.