JDK-6742159 : (launcher) improve the java launching mechanism
  • Type: Bug
  • Component: tools
  • Sub-Component: launcher
  • Affected Version: 7
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,solaris_10
  • CPU: generic,x86
  • Submitted: 2008-08-27
  • Updated: 2011-05-18
  • Resolved: 2011-05-18
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.
JDK 7
7 b38Fixed
Related Reports
Duplicate :  
Duplicate :  
Relates :  
Description
There is some room to improve the current launching mechanism, here are some
1. there a few places in the java launching code, where a lot of JNI
   calls are made,  these can be refactored into java and simplify and thereby
   reduce JNI transitions.

2. the java launcher tends to use JNI_FindClass to find classes that the launcher
   needs to initialize and process, these calls can be replaced by the JVM_FindBootClass,
   when we know for sure the classes we need are in the boot classpath. The trouble with
   JNI_FindClass is that it will use the System.loadClass, which in turn will needlessly
   search the Application Classpath for Boot Classes, by doing this we might also get
   a small startup improvement.

Comments
EVALUATION http://hg.openjdk.java.net/jdk7/tl/jdk/rev/e2c416af20bd
25-09-2008

EVALUATION Yes this is a noble effort.
27-08-2008