RFR: 8160950 Agent JAR added to app class loader rather than system class loader when running with -Djava.system.class.loader
Alan Bateman
Alan.Bateman at oracle.com
Thu Sep 8 08:40:37 UTC 2016
On 08/09/2016 09:36, David Holmes wrote:
>
> Confused again - the main class should not be loaded by the built-in
> App loader if a custom system loader was specified!
The class path you specify to the java launcher is the application class
path. The application class loader loads from that class path. If there
is a custom class loader then it has visibility to the types on the
class path by way of parent delegation. So no changes there, the only
change should be to the JPLIS agent. Note that the JPLIS agent has
always done the right thing for agents loaded into a running VM, it's
only the -javaagent/command-line where it isn't aligned with the spec.
-Alan
More information about the serviceability-dev
mailing list