Skip to content

some of the instrumentation will not always kick in #55

@shalom938

Description

@shalom938

I think that some of our instrumentation will not always work, take this for example from jaxrs instrumentation

@OverRide
public ElementMatcher.Junction classLoaderMatcher() {
return hasClassesNamed("javax.ws.rs.container.AsyncResponse");
}

if filters out class loaders that don't contain javax.ws.rs.container.AsyncResponse.
but the class loader that loads jaxrs classes is not necessarily the same class loader that loads the application classes.
it will probably work in spring boot , but some application servers already provide jaxrs classes and it may be in a lower class loader then the application classes, so this matcher can not be relied on.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions