-
Bug
-
Resolution: Fixed
-
P2
-
5.0
-
b57
-
generic, sparc
-
generic, solaris_9
The method appendToBootstrapClassLoaderSearch allows a class to be loaded by,
say the application classloader, then, after the call, by the bootstrap
loader -- in violation of classloader semantics.
There is a similar issue with appendToClassPath.
Yet, in order to reference the instrumentation support code, an agent must
be able to set these values. The only safe time to set them is before any
other class loaders have been used.
They thus must be bundled with the definition of the agent. The standard
mechanism for bundling is a JAR file.
say the application classloader, then, after the call, by the bootstrap
loader -- in violation of classloader semantics.
There is a similar issue with appendToClassPath.
Yet, in order to reference the instrumentation support code, an agent must
be able to set these values. The only safe time to set them is before any
other class loaders have been used.
They thus must be bundled with the definition of the agent. The standard
mechanism for bundling is a JAR file.
- duplicates
-
JDK-5053831 IllegalAccessError after Instrumentation.appendToBootstrapClassLoaderSearch
- Closed
-
JDK-5053975 static initializer invoked again after appendToBootstrapClassLoaderSearch
- Closed
- relates to
-
JDK-5055291 JVMTI Spec: Restrict AddToBootstrapClassLoaderSearch to OnLoad phase only
- Resolved