The customer (a tools vendor) needs a mechanism for passing command line
options to java in circumstances where the command line is not available
for modification. This includes situations where java is invoked by
fork/exec from another application or where java is embedded in a larger
application.
The primary purpose is to provide java runtime profiling, thread usage, and
code coverage in the context of large client/server applications (simple
example: servlets). The proposed uses would be causing a JVMPI module to
be loaded and/or altering the bootclasspath.
Currently there exists an environment variable _JAVA_OPTIONS which can be
used to do exactly this, although it is not documented and therefore not
public/supported. This variable appears to be used by classic and exactvm,
but not hotspot.
Please choose to make the use of this variable public, supported, and
documented.
options to java in circumstances where the command line is not available
for modification. This includes situations where java is invoked by
fork/exec from another application or where java is embedded in a larger
application.
The primary purpose is to provide java runtime profiling, thread usage, and
code coverage in the context of large client/server applications (simple
example: servlets). The proposed uses would be causing a JVMPI module to
be loaded and/or altering the bootclasspath.
Currently there exists an environment variable _JAVA_OPTIONS which can be
used to do exactly this, although it is not documented and therefore not
public/supported. This variable appears to be used by classic and exactvm,
but not hotspot.
Please choose to make the use of this variable public, supported, and
documented.
- duplicates
-
JDK-4282973 Env. variable _JAVA_OPTIONS needs to be public/documented
-
- Closed
-