JDK-6687876 : Bootstrapping of new plug-in broken with startup changes
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u10
  • Priority: P1
  • Status: Closed
  • Resolution: Fixed
  • OS: windows
  • CPU: generic
  • Submitted: 2008-04-12
  • Updated: 2010-09-08
  • Resolved: 2008-05-15
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 b23Fixed
Related Reports
Relates :  
Recent changes in 6678929 for startup time optimization have introduced an intermittent failure to bootstrap the new plug-in. The conditions under which it fails are currently unclear. The failure is intermittent but the root cause is clear; an initialization cycle was introduced that needs to be broken. The stack trace is below:

java.lang.UnsatisfiedLinkError: com.sun.deploy.config.WinConfig.getPlatformMaxCommandLineLength()I
   at com.sun.deploy.config.WinConfig.getPlatformMaxCommandLineLength(Native Method)
   at com.sun.deploy.config.Config.<clinit>(Config.java:721)
   at sun.plugin2.util.NativeLibLoader.tryLoadingFromJRE(NativeLibLoader.java:86)
   at sun.plugin2.util.NativeLibLoader.load(NativeLibLoader.java:65)
   at sun.plugin2.main.client.PluginMain.<clinit>(PluginMain.java:55)

The NativeLibLoader may not touch the Config class.

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

EVALUATION Broke an initialization cycle during startup of the new plug-in introduced with 6678929 that were causing intermittent failures to start the new plug-in on Windows, at least with development builds.