6887: Agent instrumentation fails silently if method descriptors don't match #105
This PR addresses JMC-6887. Currently when the agent is given an XML description that has an otherwise correct probe definition, but an incorrect method descriptor the instrumentation will inject the event classes but not the method, essentially failing silently.
The JFRTransformDescriptor will now track whether the ClassVisitor has found a matching method or not, and in the event that the ClassVisitor reaches the end of the class without finding a matching method it will log a warning to the user that no matching method was found. This will also catch the case where a non-existent method is specified for instrumentation, which will currently fail silently in the same way.
The text was updated successfully, but these errors were encountered:
@Josh-Matsuoka This change now passes all automated pre-integration checks. When the change also fulfills all project specific requirements, type
Since the source branch of this PR was last updated there has been 1 commit pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid automatic rebasing, please merge