[GR-71636] [GR-64510] Fix resource tracing bugs with the JVMTI tracer. #12615
+16
−12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
zipFileNameis somehow null.ZipFile.getNameshould never return a null value, so this could be JVMTI weirdness. I could not reproduce it locally. I have added a null check to avoid the transient failures.findResourceAsStreamhadmodule == null, we would pass 1 arg toReflectionProcessorinstead of the 2 expected args. I split up thehandleResourceRegistrationhelpers to disambiguate when we need to pass 1 or 2 args.