On 21/09/2024 22:14, Rafael Winterhalter wrote:
Hello,
It is a quite common need for Java agents to resolve class files for
Java classes by their name. Normally, this is done by requesting a
resource from the class loader.
I agree that the scalability issue with MR JARs deserves attention. JEP
238 pre-dates the 6 month cadence where we now add two additional
versions to search each year. I don't think this issue is really
anything to do with Java agents or the ClassLoader API, instead this is
about the JarFile implementation. Some experiments needed but it may be
more efficient to find and cache the names of the entries that are
versioned, and avoid looping through the versions altogether.
-Alan
