Re: RFR: 8253280: Use class name as class loading lock

Robert, I think you need to start a discussion on serviceability-dev about the diagnostic challenges in this area before proposing API changes to java.lang.management that have wider implications and potential interop issues. It might be that your starting point is the thread dump instead. -

RFR: 8253280: Use class name as class loading lock

When many thread try to load same class, the thread will stuck on ClassLoader.loadClass. At current jdk, the stacktrace by example program is: "Thread-1" prio=5 Id=12 BLOCKED on java.lang.Object@2e817b38 owned by "Thread-0" Id=11 at java.base@15/jdk.internal.loader.BuiltinClassLoader.loa

Re: RFR: 8253280: Use class name as class loading lock

On Thu, 10 Sep 2020 05:25:43 GMT, Robert LU wrote: > When many thread try to load same class, the thread will stuck on > `ClassLoader.loadClass`. > At current jdk, the stacktrace by example program is: > "Thread-1" prio=5 Id=13 BLOCKED on java.lang.String@724af044 owned by > "Thread-0" Id=12 >

RFR: 8253280: Use class name as class loading lock

When many thread try to load same class, the thread will stuck on `ClassLoader.loadClass`. At current jdk, the stacktrace by example program is: "Thread-1" prio=5 Id=13 BLOCKED on java.lang.String@724af044 owned by "Thread-0" Id=12 at java.base/jdk.internal.loader.BuiltinClassLoader.load